Component short names and types do not match

[atoulme]

Component(s)

No response

Describe the issue you're reporting

As reported in #24045 (comment), we currently have 2 competing standards for the short names of components.

On one hand, we have the factory type used to register the component in distros.
On the other hand, we have a name derived off the folder name of the component - called short name for this issue.

Those names do not match and this is starting to impact the following elements:

• The scope name is derived off the short name
• The Github labels are derived off the short name

The type is used everywhere else, including in configuration.

The fix is to choose one option and stick to it moving forward, which may create breaking changes.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[dmitryax]

I think it's ok to keep user configuration a bit different and allow _ for readability. but golang modules should not include them and always have exporter|processor|receiver|connector|extension suffix unless they are extension type defining interfaces like extension/storage