Instrumentation scopes

[thompson-tomo]

Is your feature request related to a problem? Please describe.
We are currently lacking a way to define telemetry which uses scopes and instead we often end up defining this attributes at the signal level which increases data storage.

Describe the solution you'd like
I want to be able to be define a collection of attributes which should be set at the instrumentation scope level and have this scope assigned to the signal.

In unresolved schema we would set:

• scope_type: string
• attributes: array ref

As part of the resolution process these scope attributes should be merged into the attribute array on the signal. The scope attributes can be distinguished from regular via the following properties:

• capture.level: signal type ie span
• capture.scope_type: scope type which adds the attribute

With scopes we could define a messaging scope containing messaging.system which is then assigned to all definitions.

This approach would enable code generation to allow setting this attributes when the language doesn't support scopes.

Describe alternatives you've considered
Setting the capture level/scope directly on the attributes at the signal level but that won't scale.

Additional context
N/a

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}