add ability to access custom CDK resource outputs from Lambda function

>**Note**: If your question is regarding the AWS Amplify Console service, please log it in the
[AWS Amplify Console repository](https://github.com/aws-amplify/amplify-console/issues)

**Which Category is your question related to?**
custom and function

**Amplify CLI Version**

7.5.2 (Why does a CLI tool need 9.35 seconds to print its version? 🤔 )

**What AWS Services are you utilizing?**

Amplify

**Provide additional details e.g. code snippets**

I'm trying to add a dependency via `backend-config.json` for my custom CDK resource. Somehow I managed to add a dependency to a function. That worked well and I deployed (`amplify push`) it. Now I've added another dependency to another custom CDK resource and whenever I try to `amplify env checkout dev` or `amplify build` or `amplify push` CLI keeps reverting my change in the `backend-config.json` and removing the second dependency. What am I doing wrong?

So far my experience with Amplify has been extremely frustrated. So much magic happening under the hood that I keep more time spent debugging and troubleshooting then I would have just building the stack with CDK.

Start by reproducing the behavior with the custom resource dependency in backend-config.json, then run amplify env checkout dev, amplify build, and amplify push to identify when the second dependency is removed. Done means the dependency remains intact through those CLI operations and the custom resource output can be accessed from the Lambda function.

Written by the indexing model from the issue text.