cmd/cue: vet's behaviour with multiple -d flags is order dependent

[jpluscplusm]

What version of CUE are you using (cue version)?

$ cue version
cue version v0.12.0

go version go1.23.5
      -buildmode exe
       -compiler gc
  DefaultGODEBUG asynctimerchan=1,gotypesalias=0,httpservecontentkeepheaders=1,tls3des=1,tlskyber=0,x509keypairleaf=0,x509negativeserial=1
     CGO_ENABLED 1
          GOARCH amd64
            GOOS linux
         GOAMD64 v1
cue.lang.version v0.12.0

Does this issue reproduce with the latest stable release?

v0.12.0 is latest.

What did you do?

env CUE_EXPERIMENT=evalv3=1

# These two cue vet invocations should fail with the same error message as they
# both validate the same data against the same pair of constraints, but with
# the constraints mentioned in different orders.

# cue vet #1
! exec cue vet .:A data.yaml -d '#B' -d '#C'
cmp stderr err

# cue vet #2
! exec cue vet .:A data.yaml -d '#C' -d '#B'
cmp stderr err
-- a.cue --
package A

#C: X: number & <10
#B: X: number & >100
-- data.yaml --
X: 4200
-- err --
X: invalid value 4200 (out of bound <10):
    ./a.cue:3:17
    ./data.yaml:1:4

What did you expect to see?

A passing test, given https://cuelang.org/docs/reference/command/cue-help-vet/:

More than one expression may be given using multiple -d flags. Each non-CUE
file must match all expression values.

What did you see instead?

# These two cue vet invocations should fail with the same error message as they
# both validate the same data against the same pair of constraints, but with
# the constraints mentioned in different orders.
# cue vet #1 (0.138s)
# cue vet #2 (0.084s)
> ! exec cue vet .:A data.yaml -d '#C' -d '#B'
FAIL: cue.vet.multipleNamedSchemasDoNotFail.txtar:12: unexpected command success