feat(sdk-node): wire up id_generator from declarative config

[MikeGoldsmith]

Which problem is this PR solving?

Wire up id_generator from the declarative config to the tracer provider. The config schema added id_generator support in v1.1.0 (open-telemetry/opentelemetry-configuration#624).

Closes #6616.

Stacked on top of #6781

This PR depends on #6781 which bumps the config schema pin from v1.0.0 to v1.1.0 (where id_generator lives). Please review and merge #6781 first so this PR's diff is clean.

Short description of the changes

• Add getIdGeneratorFromConfiguration helper in sdk-node that maps the config model's tracer_provider.id_generator to an SDK IdGenerator instance
• Currently only random is supported per the spec; unknown types warn and fall back to the SDK default (RandomIdGenerator)
• Export IdGenerator as IdGeneratorConfigModel from the configuration package so downstream consumers can reference the type
• Pass the resolved idGenerator to BasicTracerProvider

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

• 82 configuration package tests pass
• 197 sdk-node tests pass
• Full lint passes

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.53%. Comparing base (248759a) to head (b35e108).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6782   +/-   ##
=======================================
  Coverage   95.52%   95.53%           
=======================================
  Files         384      384           
  Lines       12974    12986   +12     
  Branches     2976     2979    +3     
=======================================
+ Hits        12394    12406   +12     
  Misses        580      580           

Files with missing lines	Coverage Δ
...ental/packages/opentelemetry-sdk-node/src/start.ts	97.02% <100.00%> (+0.02%)	⬆️
...ental/packages/opentelemetry-sdk-node/src/utils.ts	96.47% <100.00%> (+0.06%)	⬆️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[MikeGoldsmith]

The CI failure is from a docs link check - please could someone re-run it for me?

[trentm]

Still draft, because #6781 just merged.
However, after merging from main, this LGTM (modulo the one point on warn-and-default vs fail-fast below).

@MikeGoldsmith I'll let you respond and pull this out of draft.

[trentm]

Cool for now.

However, I think we should discuss and agree on behaviour for unknown keys.
My thoughts here: #6107 (comment)

Note (for comparison), in #6785 I made Create handling throw on unrecognized keys, e.g. https://github.com/open-telemetry/opentelemetry-js/pull/6785/changes#diff-a6c0e622127e4d2eef8ea3011fbea3abc886a8d8e4adec2a765f47127e739180R731

[trentm]

@MikeGoldsmith Please apply this patch to your PR to fix the build. In my attempt to merge from main in the GitHub UI I fixed some conflicts, but accidentally left this function in (it was moved to createSpanLimitsFromConfig in an earlier PR):

diff --git a/experimental/packages/opentelemetry-sdk-node/src/utils.ts b/experimental/packages/opentelemetry-sdk-node/src/utils.ts
index 06ad90e7b..5363eadd8 100644
--- a/experimental/packages/opentelemetry-sdk-node/src/utils.ts
+++ b/experimental/packages/opentelemetry-sdk-node/src/utils.ts
@@ -982,30 +982,6 @@ export function getIdGeneratorFromConfiguration(
   return undefined;
 }

-export function getSpanLimitsFromConfiguration(
-  config: ConfigurationModel
-): SpanLimits | undefined {
-  if (config.tracer_provider?.limits) {
-    const limitsConfig = config.tracer_provider.limits;
-    const spanLimits: SpanLimits = {};
-    spanLimits.attributeCountLimit = limitsConfig.attribute_count_limit ?? 128;
-    spanLimits.eventCountLimit = limitsConfig.event_count_limit ?? 128;
-    spanLimits.linkCountLimit = limitsConfig.link_count_limit ?? 128;
-    spanLimits.attributePerLinkCountLimit =
-      limitsConfig.link_attribute_count_limit ?? 128;
-    spanLimits.attributePerEventCountLimit =
-      limitsConfig.event_attribute_count_limit ?? 128;
-
-    if (limitsConfig.attribute_value_length_limit != null) {
-      spanLimits.attributeValueLengthLimit =
-        limitsConfig.attribute_value_length_limit;
-    }
-
-    return spanLimits;
-  }
-  return undefined;
-}
-
 export function getMeterReadersFromConfiguration(
   config: ConfigurationModel
 ): IMetricReader[] | undefined {

Once that is in, we can merge.