Add Branch features missing for apps setup to Deploy without Git where backend resources have been deployed

### Environment information

```plain text
N/A
```

### Describe the feature

Initially brought up as part of #2492

#### Background

We are deploying from an Azure DevOps Pipeline where (in simplest form) we:

- Create Amplify App using CLI:
- `aws amplify create-app --name $app_name --platform WEB --iam-service-role-arn $service_role_arn`
- Create Branch using CLI:
- `aws amplify create-branch --app-id $app_id --branch-name $branch_name --framework $framework`
- Deploy Backend:
- `npx ampx pipeline-deploy --app-id $app_id --branch $branch_name`
- Build Frontend
- Push to S3 Bucket
- Start Frontend Deployment:
- `aws amplify start-deployment --app-id $app_id --branch-name $branch_name --source-url s3://$bucket_name/$deploy_file`

Following this process under AWS Console > Amplify App > Branch > Deployments, we have `Deployed backend resources` listing all of our backend resources as expected.

For Amplify apps that are Git connected the following menu options are available when browsing a branch in the Console:

- Authentication ( `/user-management/users`, `/user-management/groups` )
- Data ( `/data/data-manager`, `/data/api-playground` )
- AI ( `/ai/setup` )
- Storage ( `/storage` )
- Functions ( `/functions` )
- UI Library ( `/ui-library` )


#### Request

Can you make these same menu options visible in the menu in our case?
As the backend resources are deployed and connected to Amplify, would like to understand if there are any reasons this couldn't be done?

#### Workaround

Manually accessing via updates to URL appears to work ok as a workaround to access these pages.
**Note:** We have only tested Authentication so far where we were able to add and remove users successfully.

### Use case

Convenience: Developers appreciate the convenient access to some of these features. They are aware they can manually visit the Deployed backend resources and work from there - but is a less convenient experience.

No repository files or tests are named. First reproduce the listed AWS CLI and npx ampx pipeline-deploy flow, then compare the Amplify Console branch menu with a Git-connected app; done means Authentication, Data, AI, Storage, Functions, and UI Library options are visible and their existing routes work for the deployed backend.

Written by the indexing model from the issue text.