Rework event names and behaviour (for React support)

[hsablonniere]

@Galimede tried to make our components work with the new experimental WC support in React.

We need to follow this issue and comment because we may need to rename our events: https://github.com/facebook/react/issues/11347#issuecomment-996872817

Document: https://docs.google.com/document/d/1wwL_YZ5TnYorEEr2Lkeh9rgbnsynDXXI7tCejVcpE6I/edit#

The other problem regards image URLs because both CRA and Vite seems to break on standard new URL("", import.meta.url) syntax!!! This is sad but it should be fixed with our work on #436.

TODO

• rename our events
  • the lower case kebab case should be enough
• should we keep the component prefixing "feature"
  • it's not really used
• should we remove the default to bubbling and only keep it for special situations (notifications, user analytics...)?
  • it would mean the component prefix is definitely useless
  • maybe we could keep the cc- prefix to avoid conflicts with native events (like click for the cc-button)

[just-boris]

The issue with colon in the event names is not unique to React. The same limitation exists in Angular: https://github.com/material-components/material-components-web/issues/4221

You better reconsider your naming convention, if you want to reach full cross-framework compatibility

[hsablonniere]

@just-boris Thanks for the heads up, I was pretty sure it worked on Angular. This is sad.