Proposed changes

Add configurableclass anddata-testid properties to all components in a dedicatedcomponent section.
This enables advanced styling use cases as well as e2e test automation.
The changes are incorporated in a way that additional component attributes can be added in the future.

Types of changes

What types of changes does your code introduce to Lowcoder?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put anx in the boxes that apply.

• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules