[exporter/exporterhelper] Migrate TimeoutConfig to schema-based configuration generated by mdatagen.

[jkoronaAtCisco]

Description

Migrate TimeoutConfig (part of exporterhelper) to mdatagen schema-based configuration. Removes the hand-written TimeoutConfig struct and NewTimeoutConfig constructor in favor of generated code driven by metadata.yaml and config.schema.json.

Authorship

• I, a human, wrote this pull request description myself.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.08%. Comparing base (a183c9c) to head (2e5c09a).

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #15505   +/-   ##
=======================================
  Coverage   91.08%   91.08%           
=======================================
  Files         733      734    +1     
  Lines       48679    48680    +1     
=======================================
+ Hits        44337    44340    +3     
+ Misses       3018     3016    -2     
  Partials     1324     1324           

☔ View full report in Codecov by Harness.
📢 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.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[dmitryax]

Nice!

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[codspeed-hq]

Merging this PR will not alter performance

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

⏩ 4 skipped benchmarks¹
🗄️ 2 archived benchmarks run²

---

_{Comparing jkoronaAtCisco:migrate_timeout_config (9afefe4) with main (a693ede)}

Footnotes

1. 4 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

2. 2 benchmarks were run, but are now archived. If they were deleted in another branch, consider rebasing to remove them from the report. Instead if they were added back, click here to restore them. ↩