Introduce a preference config for multiple hosts during db detection

[jbedell-newrelic]

If we detect multiple addresses during the connect cycle for a datastore, in the past we null the address out and pass nothing up. This config allows us to choose what to do: NONE (as we've always done), FIRST or LAST.

This came up when working with Azure SQL from inside of Azure App Services. We appeared to be getting re-directed from the requested host to a 'worker' host and thus we would send up NULL in the server.address field. Setting this to FIRST fixes that problem.

Resolves: #2493

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 70.41%. Comparing base (a38449b) to head (1f47c3d).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #2508      +/-   ##
============================================
- Coverage     70.41%   70.41%   -0.01%     
+ Complexity    10050    10049       -1     
============================================
  Files           845      845              
  Lines         40776    40788      +12     
  Branches       6186     6188       +2     
============================================
+ Hits          28712    28719       +7     
- Misses         9271     9274       +3     
- Partials       2793     2795       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.