--api-location of SWA CLI for Blazor WASM is misleading

Before filing this issue, please ensure you're using the latest CLI by running `swa --version` and comparing to the latest version on [npm](https://www.npmjs.com/package/@azure/static-web-apps-cli).

**Describe the bug**
A clear and concise description of what the bug is.

When I deploy a Blazor WASM app to ASWA, using this SWA CLI, the API location on the doc is a bit misleading. Here's the [doc](https://azure.github.io/static-web-apps-cli/docs/cli/swa-deploy#deploy-a-blazor-app)

If I run the following command, the API is not deployed.

```bash
swa deploy -a ./WebApp/bin/Release/net6.0/pubish/wwwroot -i ./ApiApp -d --env default
```

However, if I run the following command, the API is deployed properly.

```bash
swa deploy -a ./WebApp/bin/Release/net6.0/pubish/wwwroot -i ./ApiApp/bin/Release/net6.0/publish -d --env default
```

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**

- OS: WSL2 (Ubuntu 20.04) on Windows 11
- Version: SWA CLI 1.0.1

**Additional context**
Add any other context about the problem here.