Provide a more specific alternative to [data-name]

[stefanfisk]

The problem

[data-name] is super generic, and is fairly likely to clash with other third party libraries. When implementing Klaro, I had to refactor some internal code that was using that attribute.

Proposed solution

I'd prefer the attribute name to be configurable. Then it could default to [data-name] for backwards compatibility while still allowing customization.

Alternative solutions

Adding support for both [data-name] and [data-klaro-name]?

Additional context

None that I can think of.