`amplify push` doesn't read from `backend-config`, but does read from `amplify-meta`

**Describe the bug**
When running `amplify push` I expect it to consult the `backend-config.json` file, especially the `dependsOn` array for various services.

Apparently though, running `amplify env checkout …` is the magic sauce to convert the items in backend-config into amplify-meta.

**Amplify CLI Version**
4.13.1

**To Reproduce**
1. Make a change to your backend-config.json.
1. Push to the cloud.
1. Stare at your cloudformation stacks in the console, wonder why change isn't being reflected
1. Deliberately break backend-config.json
1. push to the cloud. not broken.
1. google a bunch of things
1. get frustrated
1. have dinner
1. come back, and repeat steps 1-7
1. On a whim, look at `amplify-meta.json` and see that while it's out of sync with your `backend-config.json` it's strangely in sync with what seems to be happening in the CF Template.
1. Finally have someone point out to you the 4th item #1 under https://aws-amplify.github.io/docs/cli-toolchain/quickstart#custom-cloudformation-stacks and see the bit about having to run `amplify env checkout …` to get amplify to read the changes on your local system

**Expected behavior**
The build processes associated with amplify push should read `backend-config` in a similar fashion to how it reads all of the various cloudformation templates, schemas, functions, and everything else that're kept in source control.

**Additional context**
I would really like to get these three hours back, but they're gone forever, sitting contently in a nice crowded room with all of the other (numerous) hours that I've lost to poorly documented, or buggy, pieces of the amplify codebase.