Component Accessibility Status: Enforce playwright tag naming convention

[tay1orjones]

We've established that all e2e tests ran with playwright should have one of four tags:

carbon/docs/testing.md

Lines 46 to 53 in 670dffc

	For avt tests, the test title should always include one of the following:
	| Tag | Description |
	| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------ |
	| `@avt` | High level/root tag that should wrap all avt tests. This is usually placed in a `describe` block title. |
	| `@avt-default-state` | Sub-tag of `@avt`, used to tag individual tests covering the default state of a component. |
	| `@avt-advanced-states` | Sub-tag of `@avt`, used to tag individual tests covering advanced states of a component (open/close, invalid, expanded, etc.). |
	| `@avt-keyboard-nav` | Sub-tag of `@avt`, used to tag individual tests covering keyboard navigation flows. |

I think we can use eslint-plugin-playwright to enforce this naming convention now that they've added a valid-title rule in playwright-community/eslint-plugin-playwright#167

Tasks

Beta Give feedback

1. Add eslint-plugin-playwright
2. Ensure it's only ran against the proper files, like e2e/components/accordion/accordion-test.e2e.js, and not the "e2e" test files for icons, etc that use jest and not playwright
3. Configure valid-title to ensure playwright tests with the -test.avt.e2e.js filename suffix titles always have one of the 4 allowable tags (5 if you count the blanket @avt tag we also use in the describe blocks.
4. Without a valid title, eslint should error (not warn)
5. Add some tests in the PR that show it failing on a test without a proper tag. These can be removed after the PR is approved and before it's merged.
6. Fix any remaining errors that pop up from this

[github-actions]

Thank you for submitting a feature request. Your proposal is open and will soon be triaged by the Carbon team.

If your proposal is accepted and the Carbon team has bandwidth they will take on the issue, or else request you or other volunteers from the community to work on this issue.