Consider and size the effort needed to change the terms used for levels in AQAvit

We have divided the AQA test suite into both groups and levels to support graduated and granular testing.
Current naming is:
Levels: sanity, extended, special
Groups: functional, external, openjdk, perf, system

There is a suggestion for us to consider no longer use 'sanity' as it can be considered a term that is derogatory to neurodiverse people. While we have had no actual feedback from the community on this, it is also a good time to consider if there are better ways to describe the levels of testing that we define in the AQAvit project to enhance people's understanding of what the levels mean.

This issue is to determine:
- How much effort is required to achieve this?
- Where are myriad of changes required in order to achieve this? Currently the list of repos that will require changes include but not limited to: aqa-tests, TKG, ci-jenkins-pipelines, temurin-build, aqa-test-tools, documentation, run-aqa, build-jdk, build-openj9, openj9). Additionally all Jenkins test pipelines on 2 public and 3 private servers will need to be done, as well as communicating the change to any vendors also using AQAvit (all Adoptium members), so they can update their internal servers/pipelines/processes.
- Options for new naming if we are to proceed to change to a new scheme (and repercussions of different naming choices to the amount of work required).

To be clear, this is not merely a simple name change exercise, so sizing the effort and making a plan for when such work can be achieved without disrupting many projects and teams needs to be measured.