[feat][broker] PIP-264: Add OpenTelemetry broker replicator metrics

[dragosvictor]

PIP-264

Motivation

Adds existing broker replicator metrics (documented by https://pulsar.apache.org/docs/next/reference-metrics/#replication-metrics-1) to the OpenTelemetry pipeline.

Modifications

• Adds the replication metrics, as described by [feat][doc] PIP-264: Add replication metrics reference pulsar-site#926, to the collector runs.
• Renamed Replicator#getStats to Replicator#computeStats, as it modifies the underlying object in the process. Added a simple getter Replicator#getStats for the object itself. This helps clarify the intent of the methods.

Verifying this change

• Make sure that the change passes the CI checks.

This change added tests and can be verified as follows:

• Added test ReplicatorTest#testReplicationMetrics
• Updated test ReplicatorTest#testResumptionAfterBacklogRelaxed

Does this pull request potentially affect one of the following parts:

• Dependencies (add or upgrade a dependency)
• The public API
• The schema
• The default values of configurations
• The threading model
• The binary protocol
• The REST endpoints
• The admin CLI options
• The metrics: As described in [feat][doc] PIP-264: Add replication metrics reference pulsar-site#926
• Anything that affects deployment

Documentation

• doc
• doc-required [feat][doc] PIP-264: Add replication metrics reference pulsar-site#926
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: dragosvictor#26

[lhotari]

@dragosvictor is this change intended also for 3.3.x ? Do you see any reasons why we shouldn't cherry-pick this to branch-3.3 ? The reason why I'm asking is that #23236 would apply cleanly if we first cherry-pick this PR. /cc @BewareMyPower @RobertIndie

[dragosvictor]

It's not intended for 3.3, but it won't hurt either. No problem cherry-picking it.

[lhotari]

Checked again and perhaps minimizing the risk is worthwhile if it's not needed in 3.3.x. It's not a big deal to backport #23236 to branch-3.3.