HDDS-13510. Add latency metrics for key creation operation

[sreejasahithi]

What changes were proposed in this pull request?

As part of performance improvements, new metrics to capture latency for major sub-operation in key creation are introduced. This will help in understanding where more time is spent during key creation and make it easier to troubleshoot slowness.

What is the link to the Apache JIRA

HDDS-13510

How was this patch tested?

CI: https://github.com/sreejasahithi/ozone/actions/runs/16717200562

Sample outputs of the metrics over Prometheus for a total of 2000 keys created.

[Tejaskriya]

Thanks for working on this @sreejasahithi , please find some comments below

[Tejaskriya]

LGTM, thanks for updating!

[sarvekshayr]

@sreejasahithi, please take a look at the comment below -

[sarvekshayr]

Rename endNanosCreateKeySuccessLatencyNs in both places to createKeyEndTime, capture the time in the finally block and update the latency metrics based on result.

finally {
    long createKeyEndTime = Time.monotonicNowNanos();
    long latency = createKeyEndTime - createKeyStartTime;
    if (result == Result.SUCCESS) {
        perfMetrics.addCreateKeySuccessLatencyNs(latency);
    } else {
        perfMetrics.addCreateKeyFailureLatencyNs(latency);
    }

[sarvekshayr]

LGTM

[Tejaskriya]

Thanks @sreejasahithi and @sarvekshayr