Publish fails after added new env, switched to a new env and added hosting

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### App Id

d3exe05bdo9lkk

### Region

eu-central-1

### Amplify Hosting feature

Manual deploys

### Describe the bug

Trying to publish application. It was previously connected to the bitbucket, but now I have added hosting and would like to publish manually.

```
amplify publish
✔ Successfully pulled backend environment costatest from the cloud.

Current Environment: costatest

┌──────────┬─────────────────┬───────────┬───────────────────┐
│ Category │ Resource name │ Operation │ Provider plugin │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Auth │ userPoolGroups │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Auth │ aruggaauth │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Api │ arugga │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Function │ pullRobotData │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Function │ pushRobotData │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Function │ sunset │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Function │ hobo │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Function │ IotToSQS │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Function │ SQSToIoT │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Custom │ customResources │ No Change │ awscloudformation │
├──────────┼─────────────────┼───────────┼───────────────────┤
│ Hosting │ amplifyhosting │ No Change │ awscloudformation │
└──────────┴─────────────────┴───────────┴───────────────────┘

No changes detected

? Do you still want to publish the frontend? Yes
Publish started for amplifyhosting

> front-end@0.1.0 build
> vue-cli-service build

⠹ Building for production...

WARNING Compiled with 2 warnings 15:21:56

warning

asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
This can impact web performance.
Assets:
js/chunk-vendors.13548f65.js (4.57 MiB)

warning

entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
Entrypoints:
app (4.63 MiB)
js/chunk-vendors.13548f65.js
css/app.5610ac69.css
js/app.71b79951.js

File Size Gzipped

dist/js/chunk-vendors.13548f65.js 4675.83 KiB 886.92 KiB
dist/js/polyfills-core-js.78b455bb.js 77.35 KiB 25.18 KiB
dist/js/chunk-f1fb165a.225b8fd7.js 63.78 KiB 15.14 KiB
dist/js/app.71b79951.js 57.51 KiB 15.40 KiB
dist/js/chunk-0d1060fc.cb50f79d.js 51.17 KiB 17.50 KiB
dist/js/chunk-a29b90be.caf298ac.js 50.58 KiB 9.47 KiB
dist/js/polyfills-dom.a391cc5c.js 36.74 KiB 5.86 KiB
dist/js/chunk-5980312b.880e5bd1.js 23.15 KiB 6.41 KiB
dist/js/chunk-483f0ae0.b2f1c83d.js 22.65 KiB 5.78 KiB
dist/js/chunk-5e699234.41f5cf20.js 21.44 KiB 5.99 KiB
dist/js/chunk-f969a952.5c30971f.js 19.03 KiB 6.62 KiB
dist/js/chunk-33b71d87.2f32c2d5.js 17.65 KiB 5.61 KiB
dist/js/chunk-667538b2.f966cdac.js 16.42 KiB 5.47 KiB
dist/js/chunk-e5bb031e.24ef1c4b.js 16.28 KiB 6.12 KiB
dist/js/home.ec9a1bd6.js 16.22 KiB 4.79 KiB
dist/js/chunk-2394cb10.571f5eb5.js 15.47 KiB 4.69 KiB
dist/js/chunk-3df93d1a.32a2f929.js 15.11 KiB 4.88 KiB
dist/js/chunk-627a241e.2ec8a94b.js 14.18 KiB 4.66 KiB
dist/js/chunk-0dfee8be.5b24cea5.js 13.67 KiB 4.35 KiB
dist/js/chunk-a708e4c0.3ab8c0a8.js 12.95 KiB 4.06 KiB
dist/js/chunk-533e6860.04fca290.js 12.79 KiB 4.05 KiB
dist/js/chunk-d5523222.92f6ec86.js 12.32 KiB 4.22 KiB
dist/js/chunk-507225dc.50764315.js 11.31 KiB 3.29 KiB
dist/js/polyfills-css-shim.176fed6a.js 8.57 KiB 3.40 KiB
dist/js/chunk-eb358636.9cef4d1d.js 7.99 KiB 2.46 KiB
dist/js/chunk-d4b4de5e.875beb1c.js 7.88 KiB 2.78 KiB
dist/js/chunk-d4b41fc6.b52059cb.js 6.19 KiB 2.28 KiB
dist/js/chunk-2d0dd0bc.be47342f.js 5.69 KiB 2.41 KiB
dist/js/chunk-35d5ca8f.48b0d136.js 4.13 KiB 1.49 KiB
dist/js/chunk-1a47e53c.cdce7d14.js 3.87 KiB 1.70 KiB
dist/js/chunk-2d22dbc9.8e1ae945.js 3.66 KiB 1.15 KiB
dist/js/chunk-2d0a4629.83672bfd.js 2.07 KiB 0.84 KiB
dist/js/chunk-2d0b722b.a2124a24.js 1.99 KiB 0.70 KiB
dist/js/chunk-2d0abfcf.d0d1de04.js 1.48 KiB 0.66 KiB
dist/js/chunk-2d22c8fe.bb0d4fea.js 0.91 KiB 0.46 KiB
dist/js/chunk-2d228cf2.971dcdde.js 0.90 KiB 0.49 KiB
dist/js/chunk-2d208de0.c266c424.js 0.54 KiB 0.35 KiB
dist/css/app.5610ac69.css 12.16 KiB 2.66 KiB
dist/css/home.587c9e14.css 7.99 KiB 1.99 KiB
dist/css/chunk-507225dc.db71ee09.css 4.08 KiB 1.13 KiB
dist/css/chunk-1a47e53c.3722d636.css 0.70 KiB 0.36 KiB

Images and other types of assets omitted.

DONE Build complete. The dist directory is ready to be deployed.
INFO Check out deployment instructions at https://cli.vuejs.org/guide/deployment.html

✔ Zipping artifacts completed.
✖ Deployment failed! Please report an issue on the Amplify Console GitHub issue tracker at https://github.com/aws-amplify/amplify-console/issues.
An error occurred during the publish operation: Branch costatest not found.
⚠️ Review the Amplify CLI troubleshooting guide for potential next steps: https://docs.amplify.aws/cli/project/troubleshooting/

```

### Expected behavior

to behave

### Reproduction steps

I guess create an application, connect to branch, add another backend env, add hosting, publish.

### Build Settings

_No response_

### Additional information
Branch costatest not found. Why does it search for branch?

Start with the `amplify publish` entry point and reproduce the manual deployment after switching backend environments and adding hosting. Trace why deployment searches for the `costatest` branch after the frontend build completes, using the reported error as the stopping point. Done means the documented reproduction publishes successfully without requiring an unavailable branch.

Written by the indexing model from the issue text.