Environment variables not accessible in Amplify console for app deployed using Github actions

### 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 questions](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

NEW_APP

### AWS Region

eu-central-1

### Amplify Hosting feature

Environment variables

### Is your feature request related to a problem? Please describe:

For Amplify apps that are not deployed by connecting a Git repo, we can not see the environment variables in Amplify console. This behaviour is explained as per the note on [documentation](https://docs.aws.amazon.com/amplify/latest/userguide/environment-variables.html):

`Environment variables is visible in the Amplify console’s App settings menu only when an app is set up for continuous deployment and connected to a git repository. `

However, we can add environment variables for a manually deployed app using the 'amplify update-app' command. When we try to retrieve the details of the app using 'amplify get-app' command, we can see that the environment variables are successfully associated with the app and returned in the output.

Is there a way to view/access the variables in console when the app is deployed using Github actions from Github enterprise?

### Describe how you'd like this feature to work

Environment variables section should be visible in the App settings menu in Amplify console if we are able to add or retrieve the variables using CLI commands.

Start with the linked environment variables documentation and the behavior of the `amplify update-app` and `amplify get-app` commands. Compare CLI-managed variables with the Amplify console's App settings behavior for GitHub Actions deployments. Done means defining and implementing the console access path, with documentation and validation for manually deployed apps.

Written by the indexing model from the issue text.