Use Case

As a... user
I want... a better error message when I include an unescaped special character in my connection string
So that... I know how to fix the issue

Note the spec requires this:

If the user information contains an at-sign ("@"), more than one colon (":"), or a percent-sign ("%") that does not match the rules for "pct-encoded", then an exception MUST be thrown informing the user that the username and password must be URL encoded.

We correctly throw an exception but we do not do the part about informing the user about URL encoding.

User Impact

*What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
Currently users get a confusing error message that does not tell them how to fix the issue. See NODE-3587

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind
  None

Unknowns

• questions that need to be answered to determine implementation

Acceptance Criteria

• Add a helpful error message about the percent encoding issue
• Test for the error message, cover each special character that must be escaped according to spec

Implementation Requirements

• Investigate, where this error would go, check srv resolution time, and plain uri resolution time.

Testing Requirements

Documentation Requirements

• none

Follow Up Requirements

• none