Fail eagerly on invalid labels

### Description of the feature request:

Bazel should fall immediately with a helpful stack trace when a label with an unknown apparent repo name is constructed in any context. Such labels are never useful as essentially all their methods fail, but delaying these failures makes it more difficult to fix these errors.

This would require an incompatible flag.

### Which category does this issue belong to?

_No response_

### What underlying problem are you trying to solve with this feature?

_No response_

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

_No response_

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

_No response_

### 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 HEAD` ?

```text

```

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

_No response_

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

_No response_

Start by tracing Bazel's label construction path and how incompatible flags are defined; the issue names no specific file or test. Done means invalid labels with unknown apparent repository names fail immediately in every construction context with a helpful stack trace, behind the requested incompatible flag.

Written by the indexing model from the issue text.