Amplify Hosting and CLI inconsistencies leads to broken `current-cloud-backend`

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### How did you install the Amplify CLI?

yarn

### If applicable, what version of Node.js are you using?

18

### Amplify CLI Version

10.0.0

### What operating system are you using?

Mac/Linux

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

### Amplify Categories

hosting, Not applicable

### Amplify Commands

Not applicable

### Describe the bug

I have read several times now that current-cloud-backend zip files say goodbye.

Every time I ask, they are individually hosted apps in the Amplify Console.

Structure:
- There is a backend app that is pushed via the CLI in the terminal.
- There are frontend apps that are connected to the backend app via Amplify Console.

For some reason, the DEPLOY of a connected frontend shatters the zip file. With the next deploy, the als-export.js can no longer be found and nothing works in the terminal because it hangs here:

⠏ Fetching updates to backend environment: develop from the cloud.

Because the zip cannot be read.

Who is listening here? The problem is significant and can destroy a production system.

### Expected behavior

Using the CLI in Amplify Build Settings without broken systems

### Reproduction steps

- There is a backend app that is pushed via the CLI in the terminal.
- There are frontend apps that are connected to the backend app via Amplify Console.

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

Backend App: arn:aws:amplify:eu-central-1:327300291334:apps/d36kyjopucs8j3

Frontend App: arn:aws:amplify:eu-central-1:327300291334:apps/d2v6n1oht50tox