Soft deprecate the concept of label in config and split its responsabilties

[Skaiir]

Is your feature request related to a problem? Please describe.

Currently, we have a unified concept of label that takes on two different responsibilities. It defines (in most cases) the default label a component is using. It also defines the "name" a component uses in the UI. Especially because of that second reason, we need to define it on every component, which is confusing for components that don't have a label.

Describe the solution you'd like

So for clarity and allowing us to control those two behaviors independently, I would propose that we split it into these two configs:

• componentName or simply name
• defaultLabel

To keep backwards compatibility with potential custom components, but move forwards, I think we should:

• still use config.label as a fallback in all current usages
• work on the type definitions to deprecate the property in linters

Describe alternatives you've considered

Keep it as-is?

Additional context

Somewhat related to or to be worked on with #1290
This allows us to get rid of the hardcoded solution for datetime label added here #1292

[Skaiir]

Closed via #1300