Blaze version of `unavailable_xcode_message` is being used, instead of bazel version

### Description of the bug:

`unavailable_xcode_message` from `src/main/starlark/builtins_bzl/common/xcode/semantics.bzl` is being used in Bazel, instead of from `src/main/starlark/builtins_bzl/common/xcode/semantics.bzl.oss`.

### 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.

```
DEBUG: /virtual_builtins_bzl/common/xcode/xcode_config.bzl:255:18: --xcode_version=5.1.2 specified, but it is not available locally. Your build will fail if any actions require a local Xcode. If you believe you have '5.1.2' installed, try running 'sudo xcode-select -s ',and then re-run your command. Locally available versions: 8.4.
```

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

_No response_

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

_No response_

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

_No response_

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

_No response_