[Package Issue]: Bazel.Bazelisk does not create `bazel` alias

### Please confirm these before moving forward

- [x] I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
- [x] I have not been informed if the issue is resolved in a preview version of the winget client.

### Category of the issue

Installation issue.

### Brief description of your issue

It seems Bazelisk expects that it is installed both as `bazelisk` and as `bazel`, see [its README](https://github.com/bazelbuild/bazelisk?tab=readme-ov-file#installation):
> On Windows: `winget install Bazel.Bazelisk`, `choco install bazelisk`, or `scoop install bazelisk`.
> Each adds bazelisk to the `PATH` as both `bazelisk` and `bazel`.

However the current package installation config does not actually seem to add the `bazel` alias. See also https://github.com/bazelbuild/bazelisk/issues/699.

### Steps to reproduce

1. ```
winget install Bazel.Bazelisk
```
2. ```
bazel
```

### Actual behavior

No `bazel` binary is on the PATH, only `bazelisk`

### Expected behavior

`bazelisk` should additionally be available under the name `bazel` after installation, either as symlink or in the worst case as copy?

### Environment

```raw
Windows-Paket-Manager v1.11.400
Copyright (c) Microsoft Corporation. Alle Rechte vorbehalten.

Windows: Windows.Desktop v10.0.26100.4351
Systemarchitektur: X64
Paket: Microsoft.DesktopAppInstaller v1.26.400.0
```

### Screenshots and Logs

_No response_

Start by locating the package installation configuration for Bazel.Bazelisk and compare it with the Bazelisk README's expected `bazelisk` and `bazel` commands. Reproduce the installation with `winget install Bazel.Bazelisk`, then verify that both commands resolve on PATH; the issue is done when `bazel` is available alongside `bazelisk`.

Written by the indexing model from the issue text.