Official recommendation of registering redhat.telemetry.enabled is against vscode official practices

It appears that only one extension is allowed to contribute a specific configuration property, such redhat.telemetry.enabled.

If user has more than one extension that tries to do this, it will popup a runtime warning message like below that complains about it:

AFAIK, the only solution known is not to register it and eventually use separate unique settings. The funny aspect is that we already have at least 3 extensions registering the same property:

• https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml
• https://marketplace.visualstudio.com/items?itemName=redhat.ansible
• https://marketplace.visualstudio.com/items?itemName=redhat.vscode-commons -- which to me looks like an unmaintained attempt to isolate this feature in a separate extension. Last update was many years ago.

What should we do to address this?

References

• https://github.com/microsoft/vscode/issues/226525
• https://github.com/redhat-developer/vscode-yaml/issues/1044
• https://github.com/redhat-developer/vscode-yaml/issues/564

Start by reviewing how redhat.telemetry.enabled is registered and compare the referenced VS Code, YAML, and Ansible issues. The work is done when the extensions no longer trigger the duplicate configuration-property warning and the chosen approach is documented or reflected across the affected extensions.