Filter metrics by scope

[jaydeluca]

Related to #14098 and #13468

We implemented a scope filter for span data to avoid including telemetry emitted by other instrumentations during tests, this change brings that same approach to metrics. When we process the instrumentation module, we only include the metrics that match the instrumentation scope.

After applying this change, it caught and reverted two modules that were incorrectly reporting metrics that were actually from the io.opentelemetry.netty-4.1 scope.

The new metrics file format groups the metrics under metrics_by_scope, for example:

when: default
metrics_by_scope:
  - scope: io.opentelemetry.oracle-ucp-11.2
    metrics:
      - name: db.client.connections.usage
        description: The number of connections that are currently in state described by the state attribute.
        type: LONG_SUM
        unit: connections
        attributes: 
          - name: pool.name
            type: STRING
          - name: state
            type: STRING

[jaydeluca]

the two metrics removed in this PR were both from io.opentelemetry.netty-4.1 instead of these other instrumentations