Upgrade Prometheus and Opentelemetry dependencies

[fab-10]

PR description

Upgrade Prometheus and Opentelemetry dependencies, and adjust the code accordingly.

Prometheus simpleclient upgrade introduces some changed, to follow the OpenMetrics specification, like adding the _total suffix to every counters that haven't it, and adding a _created suffixed metric to some types, while the latter is not an issue, the _total suffix is a breaking change, and requires an updated version of our official Grafana dashboard, that has been already published here, and is compatible with both metrics names.
Using the metrics by other means require a change to the tooling, for this a breaking change section has been added.

Fixed Issue(s)

[github-actions]

• I thought about documentation and added the doc-change-required label to this PR if updates are required.
• I thought about the changelog and included a changelog update if required.
• If my PR includes database changes (e.g. KeyValueSegmentIdentifier) I have thought about compatibility and performed forwards and backwards compatibility tests

[pinges]

1 Question and minor improvement suggestions

[pinges]

does this not end up with two "_total" suffixes?

[fab-10]

I understand this could be a little misleading, but internally Prometheus stores the counter name without the _total suffix, and if a name already has the suffix, it is removed, so when converting back from Prometheus to Besu names, if we remember that the name already had the suffix, we need to readd it.

[pinges]

LGTM

[macfarla]

Suggested change

- Following the OpenMetrics convention, the updated Prometheus client adds the `_total` suffix to every metrics of type counter, with the effect that some existing metrics have been renamed to have this suffix. If you are using the official Besu Grafana dashboard [(available here)](https://grafana.com/grafana/dashboards/16455-besu-full/), just update it to the latest revision, that accepts the old and the new name of the affected metrics. If you have a custom dashboards or use the metrics in other ways, then you need to manually update it to support the new naming.

- Following the OpenMetrics convention, the updated Prometheus client adds the `_total` suffix to every metrics of type counter, with the effect that some existing metrics have been renamed to have this suffix. If you are using the official Besu Grafana dashboard [(available here)](https://grafana.com/grafana/dashboards/16455-besu-full/), just update it to the latest revision, that accepts the old and the new name of the affected metrics. If you have a custom dashboard or use the metrics in other ways, then you need to manually update it to support the new naming.

[macfarla]

Suggested change

- The time that can be spent selecting transactions during block creation is not capped at 5 seconds for PoS and PoW networks, and for PoA networks, at 75% of the block period specified in the genesis. This is to prevent possible DoS attacks in case a single transaction is taking too long to execute, and to have a stable block production rate. This could be a breaking change if an existing network needs to accept transactions that take more time to executed than the newly introduced limit. If it is mandatory for these networks to keep processing these long processing transaction, then the default value of `block-txs-selection-max-time` or `poa-block-txs-selection-max-time` needs to be tuned accordingly.

- The time that can be spent selecting transactions during block creation is not capped at 5 seconds for PoS and PoW networks, and for PoA networks, at 75% of the block period specified in the genesis. This is to prevent possible DoS attacks in case a single transaction is taking too long to execute, and to have a stable block production rate. This could be a breaking change if an existing network needs to accept transactions that take more time to execute than the newly introduced limit. If it is mandatory for these networks to keep processing these long processing transaction, then the default value of `block-txs-selection-max-time` or `poa-block-txs-selection-max-time` needs to be tuned accordingly.

[macfarla]

FYI @non-fungible-nelson these debug level logs still occurring even with this upgrade ->

dev-elc-besu-teku-goerli-sally-6422-uprev-otel:~$ grep B3PropagatorExtractorMultipleHeaders /var/log/besu/besu.log
{"@timestamp":"2024-01-29T04:24:26,403","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}
{"@timestamp":"2024-01-29T04:24:26,404","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}
{"@timestamp":"2024-01-29T04:24:26,847","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}
{"@timestamp":"2024-01-29T04:24:26,862","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}
{"@timestamp":"2024-01-29T04:24:27,286","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}
{"@timestamp":"2024-01-29T04:24:27,300","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}
{"@timestamp":"2024-01-29T04:24:27,676","level":"DEBUG","thread":"vert.x-eventloop-thread-1","class":"B3PropagatorExtractorMultipleHeaders","message":"Invalid TraceId in B3 header: null'. Returning INVALID span context.","throwable":""}