I18N support proposal

[lquerel]

In theory, in a resolved registry, all fields are addressable by fully qualified and unique IDs. Therefore, we should be able to adapt Weaver—assuming we have an i18n file for each field (fully_qualified_field_id -> Translated Text)—to resolve a semconv registry for a specific language and generate documentation, code, or even configuration files accordingly.

The i18n files don't need to be fully complete. We can introduce commands to detect:

• missing translations,
• invalid fully qualified IDs,
• ...

To be defined: Develop a strategy to ensure this approach is compatible with the multi-registry project.