CSHARP-5471: Incorrectly resolving the authentication mechanism param…

[papafe]

…eters from SRV connection string

[papafe]

Hey @sanych-sun, I've tagged you since it seems you've worked on this recently.
A couple of notes:

• Not escaping the extra options while resolving the connection string seems to solve the issue.
• This means that some tests were failing due to the fact that the stringified connection string after resolving is does not have escaped values. This seems to be a minor issue, as we still parse the string correctly internally.
• I could not find anything in the specs about how should a resolved string look like, and even though Resolve is part of the public API, this could be seen as a bug fix.
• This fix solves two different cases:
  1. authMechanismProperties=TOKEN_RESOURCE:mongodb%3A%2F%2Ftest-cluster, where the option is already escaped, but does not contain encoded commas
  2. authMechanismProperties=prop:ab%2Ccd%2Cef%2Cjh, where the option is already escaped and contains encoded commas