Have a better view/structure to group jenkins jobs

[zdtsw]

(to not confuse the job for openjdk test and the job are still in progress, below, test means the former, and WIP refers to the later)

After years of creating new jobs including both production and WIP/personal jobs, our public jenkins [ci.adoptopenjdk.net](https://ci.adoptopenjdk.net/ should have a better structure to group all these jobs. The benefits are:

1. easy to navigate and find jobs
2. keep jenkins controller in a good shape: reduce disk usage for old logs and job configs
3. better tracking our job status: to know which important ones we should have them healthy
4. security. old jobs with config to certain groups e.g build,cancel,even config permission, should be revisited

some suggestion:

• both "Build Monitor" and "build status" are using jenkins dashboard plugins. Are both needed? Looks like very similar content.
• two jobs under "Dependencies" are both for the code-tools , can they be better named and put under "code-tools" view instead? Ref https://github.com/adoptium/ci-jenkins-pipelines/issues/409
• Move job "centos7_docker_image_updater" from "Infra" into "Docker Images" and rename two jobs + update descriptions.
• Rename "Failing Builds" to "Failing non-temurin builds"
• Rename "Failing Test jobs" to "Failing non-temurin test jobs"
• Do we need view "arm"?
• Rename "build-tester" to "pr-tester"
• What is "env3dev" and any jobs under is needed?
• do we need "sxa-s390xtest"? can this be moved to "work-in-progress" or rename to "Test_s390x" ?
• "git-mirrors" remove the mirror jobs that not needed and try keep the rest green
• "new-build-scripts" is the part of "OpenJDK builds" , this view is not needed
• duplicated "test_personal", check if jobs are in use, or cleanup
• move jobs e.g VagrantPlaybookCheck DockerfileCheck QEMUPlaybookCheck into "Infra" (probably more jobs)
• view "work-in-progress" should be the one for any "WIP/personal" jobs.
  1. should have better naming convention to mark jobs with owner's ID e.g <user_id>_<job_name>
  2. disable jobs if not needed by every owner
• for the jobs never been used and wont be used in the future. should be removed. e.g https://ci.adoptopenjdk.net/view/Test_external/job/Test_openjdk17_hs_extended.external_x86-64_linux_lucene-solr/

[zdtsw]

some jobs need to be cleaned up which aint useful for old jdk version or created by mistake

• openjdk18
• build-scripts/jobs/jdk18u/*
• prototype