Move `compile-pass` tests to `check-pass` or `build-pass`

[cramertj]

compile-pass was the old way to assert that UI tests were able to successfully build. However, it would do a full build of the code, including codegen and linking. Many of our tests don't need this, however, and should instead use the new check-pass, introduced in #61778. For tests that exercise codegen and linking, build-pass can be used instead.

As a first step, it would be good to remove compile-pass to prevent users adding new tests that unconsciously take a dependency on codegen/linking, and push them to use check/build-pass to make the distinction explicit.

To do this, we'd like to start with a mass migration of compile-pass tests to build-pass (rather than check-pass because we don't want to accidentally stop testing codegen/linking functionality). However, we don't want to lose the distinction between tests which are intentionally build-pass and those that have been automatically migrated, so automatically-migrated tests should include a note like // build-pass (FIXME(this-issue-#): could be check-pass?) or similar.

Once that's done, we can remove compile-pass and work on moving over the FIXME-tagged tests to either check-pass or remove the FIXME.

[Centril]

• Mass migrate // compile-pass annotations to // build-pass (FIXME(62277): could be check-pass?).

• Remove // compile-pass from compiletest.

• Triage // build-pass annotations re. whether they should be // check-pass. (Update some build-pass ui tests to use check-pass where applicable #66087)

[Centril]

cc @petrochenkov