Add new entity to the YAML model for "stand alone" attributes

[joaopgrassi]

The semantic conventions SIG has agreed to go forward with the proposal open-telemetry/semantic-conventions#197 to decouple the attribute definition from its usage in the conventions. Essentially, we will achieve a "registry" of attributes that are standalone and then can be referenced by any convention.

During the initial split for HTTP open-telemetry/semantic-conventions#208 we saw that the current YAML model is not fit for this. The attributes entity today have many properties such as requirement level that are not relevant for the registry. For ex, the requirement level is rendered in markdown, which does not apply for the registry concept.

As a temporary workaround, @AlexanderWert worked on #190 to unblock working on the registry "move". But in the long run, we should have a better solution, that involves modifying our YAML model and introduce a new entity for such attribute registry type.

@AlexanderWert also worked on a proposal for this, which can be seen in #191

Once we have implemented the feature in YAML, we should consider removing the workaround done in #190.

[Oberon00]

IMHO, attribute_group could (should?) be adapted to fulfill these instead of adding another type

[lmolkova]

Related to #290

[jsuereth]

Closing as wontfix. We've migrated attribute registry to weaver with policy enforcement. I think there's an overall question of how we evolve our YAML model to better account for a registry and formalize things in group, e.g.