Selected static web site not filtered by resource group

SWA version: 2.0.6

**Are you accessing the CLI from the default port `:4280` ?**

- [ ] No, I am using a different port number (`--port`) and accessing the CLI from that port
- [x] Yes, I am accessing the CLI from port `:4280`

> Make sure you are accessing the URL printed in the console when running `swa start`!

**ℹ️ NOTE: Make sure to enable debug logs when running any `swa` commands using `--verbose=silly`**

**Describe the bug**
I have 2 resource groups, both with a static web app having the same name. When I run the deploy command, specifying the output folder and the explicit resource group and app name, the website is always deployed to the same resource group.

**To Reproduce**
Steps to reproduce the behavior:

1. Create resource group `a-rg`
2. Create static web app `same-name-swa` within resource group `a-rg`
3. Create resource group b-rg
4. Create static web app `same-name-swa` within resource group `b-rg`
5. Run `swa deploy .out\ --resource-group b-rg --app-name same-name-swa`
Actual behavior:
Website is deployed to static web app in resource group `a-rg`
Expect behavior:
Website is deployed to static web app in resource group `b-rg`

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

- OS: Window 11

Beginne beim Einstiegspunkt `swa deploy` und verfolge, wie `--resource-group` und `--app-name` die Static Web App auswählen. Reproduziere das Szenario mit den zwei Ressourcengruppen aus dem Issue und überprüfe anschließend, dass die Bereitstellung mit `--resource-group b-rg --app-name same-name-swa` auf die App in `b-rg` und nicht auf die gleichnamige App in `a-rg` zielt.

Vom Indexierungsmodell aus dem Issue-Text verfasst.