Illegal ambiguous match with flags

### Description of the bug:

When combining a flag with another `config_setting`, Bazel seems to think that one is not a more specialized version of the other. However, I can't understand why that is.

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

I have a simple repro case here: https://github.com/jjwon0/bazel-select-mre/

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

linux

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

release 6.1.0

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

n/a

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

```text
n/a
```

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

I read through all the recent issues related to `select()` but nothing seemed to be an exact match. I also read the configuration docs through a few times.

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

It's totally possible that I don't understand what it means to be specialized, but I would have thought that matching one of many attributes in a `config_setting_group` would do the trick.

This also doesn't seem to happen on Bazel 5.1.1.