[SqlClient] Refactor SqlConnectionDetails

[alanwest]

This is a refactor that extracts SqlConnectionDetails from the SqlClientTraceInstrumentationOptions class. Evaluating connection details is not specific to spans - it will also be used for DB metrics.

This PR is similar to what is done in #2026. I will deal with the merge conflicts on #2026.

There's a whole bunch that I don't like about the tests for this instrumentation. A lot of copy and paste for .NET vs. .NET Framework tests and inconsistent test cases covering them. This PR does not attempt to address improving tests. I'll do this in a follow on PR before stabilization.

There's also a small bug fix where server.port was captured as a string instead of an int.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.36%. Comparing base (71655ce) to head (df3190e).
Report is 545 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2233       +/-   ##
===========================================
+ Coverage   73.91%   91.36%   +17.44%     
===========================================
  Files         267        8      -259     
  Lines        9615      301     -9314     
===========================================
- Hits         7107      275     -6832     
+ Misses       2508       26     -2482     

Flag	Coverage Δ
unittests-Instrumentation.SqlClient	91.36% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...qlClient/Implementation/SqlActivitySourceHelper.cs	100.00% <100.00%> (ø)
...ient/Implementation/SqlClientDiagnosticListener.cs	87.35% <100.00%> (ø)
...n.SqlClient/Implementation/SqlConnectionDetails.cs	100.00% <100.00%> (ø)
...ent/Implementation/SqlEventSourceListener.netfx.cs	88.23% <100.00%> (ø)
....SqlClient/SqlClientTraceInstrumentationOptions.cs	100.00% <ø> (ø)

... and 267 files with indirect coverage changes

[CodeBlanch]

There is a RegEx source generator available now. Doesn't have to be part of this PR, but we should probably move to that on targets where it is available. Reason being is I assume it gives best perf across the board but especially when AoT is in play and compilation is not available (assuming RegEx falls back to interpreter when dynamic code isn't available).

Some reasons listed here why it should be used:
https://learn.microsoft.com/dotnet/standard/base-types/regular-expression-source-generators#when-to-use-it

[alanwest]

#2234

[CodeBlanch]

LGTM