Metadata Telemetry scope allowlist

[jaydeluca]

Related to #13468

There are some instrumentations that use instrumenters or Telemetry classes from other instrumentation modules, and the resulting telemetry has a scope that does not match the instrumentation name. For example, the armeria-grpc-1.14 instrumentation installs Client and server interceptors from the grpc-1.6 instrumenation library, and therefore the resulting spans have a scope of io.opentelemetry.grpc-1.6

This causes issues with the SpanParser when trying to show telemetry emitted, because we are filtering out all telemetry signals that don't match the scope of the instrumentation module we are processing.

I think in cases like this, it's useful to have that telemetry documented, even if the scope doesn't match, since it is armeria-grpc-1.14 installing those filters and enabling the telemetry.

So I added a new capability to specify a scopeAllowList so that you can define additional scopes to include in telemetry collection for a given scope (for example to allow showing the telemetry from grpc-1.6 for armeria-grpc-1.14).

[trask]

I'd suggest not using inheritance for this

instead maybe something like (didn't think too much about names so feel free to pick others)

Suggested change

	if (spansByScope.getScope().equals(targetScopeName)
	|| scopeAllowList
	.getOrDefault(targetScopeName, Set.of())
	.contains(spansByScope.getScope())) {
	if (AllowedScopes.contains(spansByScope, targetScopeName)) {