Use the correct SDK EventSource method to log invalid environment variable

[utpilla]

Related to #4516

This PR sets the correct method to be used to log when the SDK runs into an invalid environment variable read in the Configuration extension method: TryGetIntValue.

Changes

• OpenTelemetry SDK uses ConfigurationExtensions method: TryGetIntValue in multiple files such as BatchExportActivityProcessorOptions, BatchExportLogRecordProcessorOptions, and PeriodicExportingMetricReaderOptions
• TryGetIntValue expects the Action LogInvalidEnvironmentVariable to be set if a component wants to log this information:
• Fix issue of multiple instances of OpenTelemetry-Sdk EventSource being created #4586 missed out on configuring the action to log when environment variable value is invalid

Merge requirement checklist

• CONTRIBUTING guidelines followed (nullable enabled, static analysis, etc.)
• Unit tests added/updated
• Appropriate CHANGELOG.md files updated for non-trivial changes
• Changes in public API reviewed (if applicable)

[codecov]

Codecov Report

Merging #4649 (d08b226) into main (f95c689) will increase coverage by 0.02%.
The diff coverage is 100.00%.

❗ Current head d08b226 differs from pull request most recent head 213e99c. Consider uploading reports for the commit 213e99c to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4649      +/-   ##
==========================================
+ Coverage   84.97%   85.00%   +0.02%     
==========================================
  Files         314      314              
  Lines       12685    12689       +4     
==========================================
+ Hits        10779    10786       +7     
+ Misses       1906     1903       -3     

Impacted Files	Coverage Δ
src/OpenTelemetry/Sdk.cs	100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes