[sdk-node, resources] support `resource.detection/development.attributes` from declarative config

[trentm]

The declarative config schema ExperimentalResourceDetection (https://opentelemetry.io/docs/specs/otel-config/types/#type-experimentalresourcedetection) supports an attributes property which can define attributes to include or exclude from resource detectors.

For example, here is a declarative config snippet that would exclude detected resource attributes host.name and any attributes matching the glob pattern process.command*

file_format: '1.1'
resource:
  attributes:
    - name: foo
      value: bar
  detection/development:
    attributes:
      excluded:
        - "host.name"
        - "process.command*"
    detectors:
      - service:
      - host:
      - process:

This might involve adding some support to the resources package to support this. Because some resource attributes can be async, we cannot synchronously run the detectors and then filter before returning a Resource to use.

[pri12ya871]

I'd like to work on this — could you assign it to me?

On the async point in your last paragraph: since a detected Resource's attributes can settle asynchronously, I take it the include/exclude lists have to be applied to the resolved attributes rather than to detector output up front. Would you rather that live in the resources package — something that wraps a detected Resource and applies the lists as its async attributes settle — or in sdk-node, at the point where declarative config is translated into detectors?

Two smaller things I'd want to pin down before writing anything:

1. When both included and excluded are present, is the intended order include-then-exclude, so excluded wins on an overlap?
2. Which glob syntax should I match — just * and ? as in the config spec, or something broader?

Happy to follow whatever the spec already settles if I've missed it.

[JamieDanielson]

Note: currently blocked on #6989