[SDK] Support independent programmatic configuration

[dbarker]

Fixes #4134 and follow up from ##3655 (review)

Break out the programmatic configuration to its own library so it can be used without the ryml dependency.

Changes

• Creates the programmatic configuration target (configuration_core)
• Adds configuration_core to the CMake install tests
• Adds programmatic_configuration_test.cc
• Fix issues found with the new test
  • LoggerConfigurator supporting min severity and trace based fields
  • Initialize members of config classes to the spec default constants.
  • Set the default parent based root sampler to always_on
  • Set the default sampler to parent based always on
  • Set all batch processor options that the user configured
  • Handle default metric stream aggregation
• Fix the cppcoreguidelines-pro-type-member-init warnings in configuration and sdk files used by the tests.
• Update INSTALL doc for the configuration targets

For significant contributions please make sure you have completed the following items:

• CHANGELOG.md updated for non-trivial changes
• Unit tests have been added
• Changes in public API reviewed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.19%. Comparing base (676c9dc) to head (fa19cca).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4240   +/-   ##
=======================================
  Coverage   81.19%   81.19%           
=======================================
  Files         444      444           
  Lines       18880    18880           
=======================================
  Hits        15328    15328           
  Misses       3552     3552           

Files with missing lines	Coverage Δ
...k/include/opentelemetry/sdk/metrics/meter_config.h	100.00% <ø> (ø)

🚀 New features to boost your workflow:

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

[dbarker]

This is a case where zero is a valid value for the option so it is not a great way to indicate "not set". Instead of using zero in all these config structs to indicate not set, we may consider either setting the spec defaults (which the SDK/exporter options structs also do) or bring in an std::optional/nostd::optional type.

[dbarker]

The spec seems clear on the in memory configuration model.

https://opentelemetry.io/docs/specs/otel/configuration/sdk/#in-memory-configuration-model

If a property is present and the value is null, Create MUST use the nullBehavior, or defaultBehavior if nullBehavior is not set.

Changes:

• Updated the config files to define and initialize to the default values provided by the configuration schema as defaultBehavior .
• Updated the parser to use the config class defaults.
• Added TODOs where the current implementation defaults differed from the schema.

[dbarker]

This PR will be broken up into multiple PRs (will edit with PR links).

1. Tests for SdkBuilder, ConfiguredSdk, and integration tests for programmatic configuration along with fixes to the SdkBuilder they exposed.
   • [CONFIGURATION] Programmatic configuration use case tests and fixes #4243
2. Move spec defaults from the configuration_parser.cc to each configuration struct.
   • [CONFIGURATION] Define and set spec default values in configuration objects #4244
3. CMake separation of configuration_core and configuration
4. CMake component cleanup and deprecation of the "builder" components since the sdk will now include the builder interfaces.