OTI to ChIP migration

[pkcll]

Context

Currently legacy telemetry is sent via OTI ingress (see https://github.com/smartcontractkit/chainlink/tree/develop/core/services/telemetry). Extend existing legacy telemetry sending mechanism to be able to use ChIP ingress instead of OTI

Jira: https://smartcontract-it.atlassian.net/browse/INFOPLAT-2732

What

• Implement chipIngressBatchClient/Worker for legacy telemetry
• Use ChIP ingress public ingress to ingest legacy telemetry

Why

OTI-to-Beholder migration

[github-actions[bot]]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[cl-sonarqube-production[bot]]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)
C Security Rating on New Code (required ≥ A)
11 New Major Issues (required ≤ 5)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarQube IDE