Completely custom pipeline without any Amplify wrappers or images

### 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 removed any sensitive information from my code snippets and submission.

### Amplify Hosting feature

Deployments

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

Can Amplify team publish a guide how to deploy resources without using any Amplify-forced build configurations or services?

This will allow customers to setup pipeline the way it works for our environments.

There are three main parts, backend deployment, outputs export and the front-end deployment. The most problematic part is front-end deployments due to magical transfers of build output somewhere on CDN.

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

I'd like to have CDK construct on top of the Pipelines

so I can run just one command to deploy pipeline and be able to adjust it as needed without constantly required to mess with build settings in the console, deal with custom docker images, custom yml files and curl hacks

`npx cdk deploy amplifyApp-main/prod/pipeline`

The pipeline will build and deploy my dev env and optionally can proceed to deploy other environments.

Thank you

Start with FAQ.md and the issue's three deployment areas: backend deployment, outputs export, and front-end deployment. Review the proposed amplifyApp-main/prod/pipeline entry point and determine the scope of a CDK construct that avoids Amplify-forced build settings, images, YAML files, and console configuration. Done would require an agreed design and documented end-to-end deployment flow.

Written by the indexing model from the issue text.