defining a classname in the feature may create name conflicts

[ethernian]

defining a class in the button definition may create a name confict between different features (or different versions of the same feature).

We may have similar problems with other names defined by loaded modules but expected to be unique in the broader space (inside the document, for example).

https://github.com/dapplets/typescript-examples/blob/40d0fa8cf4d2aaaf16d4f7fad46a357fd61c8f56/src/TwitterFeature2/index.ts#L116-L118

Maybe, we need to use namespaces for each loaded feature as prefixes for class names or define unique names automatically like Symbols or by some factory provided by Core or Adapter?

[ethernian]

maybe, introduce an ID instead of class (or in addition to)?