INFOPLAT-2449: Use chainlink-common otelzap core in chainlink global logger

[kirqz23]

What

Use chainlink-common otelzap core in chainlink global logger for exporting logs through beholder to Otel and Loki.
Enables early logger setup with OTel support without requiring chainlink logger recreation when beholder is initialised. Leveraging atomic core for swapping noop core with otel core when Beholder is ready.

Related PRs:

1. INFOPLAT-2282: Add beholderNoopLogerProvider and LogStreamingEnabled flag to control emitting logs chainlink-common#1263
2. INFOPLAT-1035: logger implement otelzap chainlink-common#1359
3. INFOPLAT-2672: beholder: config option to enable streaming logs to OTel in LOOP chainlink-common#1486
4. INFOPLAT-2672: beholder: config option to enable streaming logs to OTel in core #19005
5. Beholder OTel logs streaming for LOOPP's chainlink-common#1566
6. INFOPLAT-2449 add telemetry log level config option #19775
7. beholder: add telemetry LogLevel config option for log streaming chainlink-common#1591

How

1. Early init of beholder and it's dependencies in before hooks for subcommands. We introduced common BeforeNode() and AfterNode() function that setups and clears all dependencies including database, datastore, keystore and beholder. The reference to db, keystore and datasource is stored in the shell.
2. We integrated chainlink-common otelzap package with zap core for otel. To be able to initilize logger earlier (before beholder is ready in root node command), we leverage atomic functionality to swap atomic core for otel whenever beholder is ready in atomic operation to avoid race condition. Additionally, we implemented NewWithCores() that accepts additional cores (besides default one) that helped us achieve above.

[github-actions]

👋 kirqz23, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

[cl-sonarqube-production]

Quality Gate passed

Issues
1 New issue
1 Fixed issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube