feat(koa): Adds support to ignore a span by its layer name

[MrFabio]

Which problem is this PR solving?

• Adds ignoreLayersName option to instrumentation constructor config to allow layers to be ignored by its name.
• Currently we have the ignoreLayersType config, this new one will run after this check.
• It is useful if we want to ignore some layers like logger, allowedMethods, and some ones with no name. It also helps with reducing the number of spans.

Short description of the changes

• Defines KoaInstrumentationConfig with ignoreLayersName which is an array of string (layer names):
• Utils module with isLayerNameIgnored to check if a layer should be ignored by the name
• Modifies _patchLayer to check if the layer is ignored by the config

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: MrFabio / name: Fábio Gomes (6485e10)

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.42%. Comparing base (dfb2dff) to head (6485e10).
Report is 190 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2028      +/-   ##
==========================================
- Coverage   90.97%   90.42%   -0.56%     
==========================================
  Files         146      148       +2     
  Lines        7492     7341     -151     
  Branches     1502     1528      +26     
==========================================
- Hits         6816     6638     -178     
- Misses        676      703      +27     

Files	Coverage Δ
...ode/opentelemetry-instrumentation-koa/src/types.ts	100.00% <ø> (ø)
...ode/opentelemetry-instrumentation-koa/src/utils.ts	100.00% <100.00%> (ø)
...lemetry-instrumentation-koa/src/instrumentation.ts	94.25% <66.66%> (-1.15%)	⬇️

... and 60 files with indirect coverage changes

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.

[MrFabio]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature. Are you familiar with this package? Consider becoming a component owner.

@blumamir can you help?

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.