Bazel 7.0: Java Toolchain Resolution for Bazel Ignores Java Flags

### Description of the bug:

To set and pin the Java toolchain to Java 11, Google documentation says to use

```
common --java_language_version=11
common --java_runtime_version=remotejdk_11
common --tool_java_language_version=11
common --tool_java_runtime_version=remotejdk_11
common --host_javabase=@bazel_tools//tools/jdk:remote_jdk11
common --javabase=@bazel_tools//tools/jdk:remote_jdk11
common --host_java_toolchain=@bazel_tools//tools/jdk:toolchain_java11
common --java_toolchain=@bazel_tools//tools/jdk:toolchain_java11

```
We observe that Bazel will not respect these flags in 7. However, this configuration works in Bazel 6.4.0.

### Which category does this issue belong to?

_No response_

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

See branch at https://github.com/EdbertChan/SimpleBazelAndroidApp/tree/demonstrate_bazel_7_aquery

### Which operating system are you running Bazel on?

MacOS

### What is the output of `bazel info release`?

release 7.0.0-pre.20230906.2

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

_No response_

### What's the output of `git remote get-url origin; git rev-parse master; git rev-parse HEAD` ?

_No response_

### Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.

Yes. Last worked on Bazel 6.4

### Have you found anything relevant by searching the web?

N/A

### Any other information, logs, or outputs that you want to share?

When running with --toolchain_resolution_debug=., it looks like the resolution is overwritten at the last moment.

For instance, the log will be filled with

`INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/jdk:runtime_toolchain_type -> toolchain @remotejdk11_macos_aarch64//:jdk
`

But then the resolution gets set to remotejdk17. This does not make sense: it actually rejects the remotejdk11_macos_aarch64 when it has previously accepted and selected it.

Here is a portion of the toolchain debug:
```

INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/jdk:runtime_toolchain_type -> toolchain @remotejdk11_macos_aarch64//:jdk
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_linux//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_linux_aarch64//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_linux_ppc64le//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_linux_s390x//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_macos//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_macos_aarch64//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_win//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk11_win_arm64//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_linux//:jdk; mismatching values: linux, x86_64
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_linux_aarch64//:jdk; mismatching values: linux
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_linux_ppc64le//:jdk; mismatching values: linux, ppc
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_linux_s390x//:jdk; mismatching values: linux, s390x
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_macos//:jdk; mismatching values: x86_64
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: execution @local_config_platform//:host: Selected toolchain @remotejdk17_macos_aarch64//:jdk
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_win//:jdk; mismatching values: windows, x86_64
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk17_win_arm64//:jdk; mismatching values: windows
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk20_linux//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk20_linux_aarch64//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk20_macos//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk20_macos_aarch64//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Type @bazel_tools//tools/jdk:runtime_toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @remotejdk20_win//:jdk; mismatching config settings: prefix_version_setting
INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/jdk:runtime_toolchain_type -> toolchain @remotejdk17_macos_aarch64//:jdk
```

Start with the linked SimpleBazelAndroidApp branch and reproduce the behavior using the listed Java flags on Bazel 7.0.0-pre.20230906.2, comparing it with Bazel 6.4.0. Run with --toolchain_resolution_debug=. and inspect where the selected remotejdk11 toolchain becomes remotejdk17; done means the regression is reproduced and toolchain selection respects the requested Java 11 configuration.

Written by the indexing model from the issue text.