Do not match pipe as port separator

[jnyrup]

Description

Using grep.app I noticed that a slightly incorrect regex was introduced in #10340 to match "host and port".

[:|,] matches any of the characters :, '|' or ,, where the updated regex [:,] only matches : or ,.

Fixes # (issue)

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue (consider using one of the following templates):
      • New (or update) doc-idea template
      • New breaking-change template
      • New diagnostic template
  • No

[Copilot]

Pull Request Overview

This PR fixes a regex pattern in the ConnectionStringParser that was incorrectly matching pipe characters ('|') as valid port separators. The change ensures only colon (':') and comma (',') are recognized as valid separators between host and port in connection strings.

Key Changes

• Updated the regex pattern to remove pipe character from the character class
• Changed [:|,] to [:,] to match only colon or comma separators

[davidfowl]

Good catch