feat: Enable name attribute as an independent selector config

[mike-plummer]

Currently, the name attribute would only be utilized in a generated selector if a class-based option cannot be created. For UI Coverage several issues exist where we need to generate selectors around form fields and those can be identified in a more stable manner using the name attribute in situations where id is not present.

https://cypress-io.atlassian.net/browse/CYCLOUD-2174?focusedCommentId=30643
https://cypress-io.atlassian.net/browse/CYCLOUD-2111

I've chosen to break this out as a separate option in parallel with the existing attributes option - using that existing option would require elevating attributes above class and would have a much broader impact on the style & structure of generated selectors beyond the very targeted behavior change I'm looking for.

Reviewer note: I think I don't have to do a CSS.escape on the attribute value here since it's inside quotes, but correct me if I'm wrong

[CLAassistant]

All committers have signed the CLA.

[chrisbreiding]

Looks good 👍 This should be considered a breaking change since we're changing the default selectorTypes, right?

[mike-plummer]

Looks good 👍 This should be considered a breaking change since we're changing the default selectorTypes, right?

Good point - is it enough to throw a "BREAKING CHANGE:" into the squash commit body?

[chrisbreiding]

Good point - is it enough to throw a "BREAKING CHANGE:" into the squash commit body?

I'd put some text after it just to be safe. I'm not sure how particular semantic-release is in regards to that. Something like this for the commit:

 feat: Enable name attribute as an independent selector config #6 
 
 BREAKING CHANGE: Default selectorTypes is now ['id', 'name', 'class', 'tag', 'nth-child']

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀