Checklist for declaring stability for messaging semantic conventions

[pyohannes]

Separate experimental parts from stable messaging semantic conventions

When messaging semantic conventions are declared stables, some parts of the conventions should be excluded and remain in an experimental state.

This issue collects all parts that should be marked as experimental prior to declaring messaging semantic conventions stable:

• All references to "Process" spans (Add semantic conventions for "Process" spans for messaging scenarios #657)
• All references to "Settle" spans (Add conventions for settlement spans for messaging #621)
• The following attributes:
  • messaging.message.body.size (Change rpc and messaging body/payload size attributes from recommended to opt-in? #474)
  • messaging.message.envelope.size (Change rpc and messaging body/payload size attributes from recommended to opt-in? #474)
  • network.protocol.name (Messaging: protocol name requirement level and defaults #504)
  • network.protocol.version (Messaging: protocol name requirement level and defaults #504)
  • messaging.destination.temporary and messaging.destination.anonymous (Messaging: do we need messaging.destination.temporary and/or messaging.destination.anonymous attributes? #1126)

Finally, also any stability present on any stabilized messaging documents need to be removed.

Open tickets against instrumentations

As suggested in this comment, tickets against all existing messaging instrumentations in OpenTelemetry repositories need to be opened, outlining the changes and required actions

[joaopgrassi]

The last item in this list was done #1442 (.size attributes as Opt-In), so closing this one.