Feature add applyCustomAttributesOnMetric on HTTP Instrumentation

[evan361425]

Which problem is this PR solving?

Fixes #4317

add applyCustomAttributesOnMetric to hook metrics attributes.

Short description of the changes

interface HttpCustomMetricAttributeFunction {
  (span: Span, spanKind: SpanKind, metricAttributes: MetricAttributes): void;
}

Not same as origin issue:

export interface HttpCustomAttributeFunction {
  (
    span: Span,
    metricAttributes: Attributes,
    request: ClientRequest | IncomingMessage,
    response: IncomingMessage | ServerResponse
  ): void;
}

This is because _closeHttpSpan has only these arguments (Span and SpanKind).

If we really needed the request, more codebase need to change and verify.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Verify error callback won'y break the code

Checklist:

• Followed the style guidelines of this project
• Unit tests have been added
• Documentation has been updated

[linux-foundation-easycla]

• ✅login: evan361425 / (da2206a)

The committers listed above are authorized under a signed CLA.

[pichlermarc]

Hi, thanks for your interest in contributing to OTel JS.

In order to add this feature, we need to ensure that it is safe for everyone to use before we release it into the wild, and there's some prerequisites we need before we can accept your contribution (namely #4095, #4096). Please head on over to #5051 to get a full summary of the current status - I'll keep updating that issue as we go through the process of discussing how we'd like to proceed with this.

Once we've decided if we want to add this or not, we'll create type:feature and type:feature-tracking issues to signal that this feature is ready for implementation.