Feature description

While data-testid is the most common attribute name for test ids, but it's not the only one. Other vendors use other attribute names, e.g. data-cy in Cypress and users might have adopted their own naming convention. Begin able to configure the name of the attribute k6 Studio should look for while recording would give users more flexibility and

Suggested solution (optional)

In its simplest form, this would mean having a way of configuring a set of attributes that should be considered test ids. These attributes would be recorded alongside all other selectors. Users could then decide at script generation time which selectors to prioritize.

NOTE: Due to how scripts are loaded in extensions, this would likely need to be a CDP feature only.

Already existing or connected issues / PRs (optional)

No response