Bazel: fix non-swift macOS builds

[redsun82]

Now the swift-specific compilation options are contained in a transition applied only to swift targets.

A transition is required for the macOS -arch options, because we need all dependencies that are linked into swift targets to have those. While other options (-fno-rtti and -std=c++20) could work with a simple cc_{binary,library} attribute injection, it was preferred to use one mechanism only.

This is meant to be cleaned up in a later PR with respect to the TODO: the bazel transition used for Swift is inspired by what we use in the internal repo, but has some differences:

• the internal binary is removed from the runfiles, as otherwise codeql_pkg_runfiles had a conflict on it
• the transition works on cc_library as well
• the transition forwards the CcInfo provider as well

Also added new triggers to local go CI to detect this kind of problem earlier next time.

One drawback of a transition-based approach is that bazel build //swift/... ceases to work, because it picks up the internal transition targets without the proper compile options. This also means that bazel test //swift/... now requires --build_tests_only.

[criemen]

LGTM, assuming that defining a select object and injecting that via _wrap_cc is too complicated/cumbersome, or doesn't work for some reason.

[criemen]

(sorry about the conflict)

[criemen]

Reapproving