Rehome 35 tests/ui/issues/ tests to other subdirectories under tests/ui/

[Oneirical]

#143902 divided into smaller, easier to review chunks.

Part of #133895

Methodology:

1. Refer to the previously written tests/ui/SUMMARY.md
2. Find an appropriate category for the test, using the original issue thread and the test contents.
3. Add the issue URL at the bottom (not at the top, as that would mess up stderr line numbers)
4. Rename the tests to make their purpose clearer

The URL addition at the end, as well as moving around the auxiliary files and editing the stderr files with the new filename, were done using a Python script.

Inspired by the methodology that @Kivooeo was using.

r? @jieyouxu

[rustbot]

jieyouxu is not on the review rotation at the moment.
They may take a while to respond.

[rustbot]

There are changes to the tidy tool.

cc @jieyouxu

[rust-log-analyzer]

The job tidy failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[TIMING] core::build_steps::tool::Tidy { compiler: Compiler { stage: 0, host: x86_64-unknown-linux-gnu, forced_compiler: false }, target: x86_64-unknown-linux-gnu } -- 0.000
fmt check
fmt: checked 6161 files
tidy check
tidy error: `ISSUES_ENTRY_LIMIT` is too high (is 1616, should be 1575)
Checking tidy rustdoc_json...
Running eslint on rustdoc JS files
No error code explanation was removed!
tidy: Skipping binary file check, read-only filesystem
removing old virtual environment
---
All checks passed!
checking python file formatting
28 files already formatted
checking C++ file formatting
some tidy checks failed
Command has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:01:21
  local time: Thu Jul 17 21:53:35 UTC 2025
  network time: Thu, 17 Jul 2025 21:53:36 GMT
##[error]Process completed with exit code 1.
Post job cleanup.