feat: add resource parameter map to backend-config.json

[edwardfoyle]

Description of changes

Places a map of parameter names and which resources they relate to in the backend-config.json file. There are a few oddities with how this had to be implemented:

1. There are some places where the keys of the backend-config.json file is used as a list of categories (such as in amplify status) so I modified stateManager.getBackendConfig to only return the parameters key if a special flag is specified. This flag is only used by the new parameter map manager class.
2. Writing backend-config.json to disk is not stable -- the same object may be serialized with keys in different order depending on how the object was constructed. A new flag has been added to JSONUtilities.stringify to specify that object keys should be sorted to ensure deterministic serialization
3. The above had the side effect of changing how the types file for custom resources is generated so that is also modified to use the stable flag in JSONUtilities (and removed an ejs template in the process)

Issue #, if available

Description of how you validated changes

Added unit tests and existing e2e tests pass

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
• Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[lgtm-com]

This pull request fixes 1 alert when merging 024922d into 5ebbc72 - view on LGTM.com

fixed alerts:

• 1 for Unused variable, import, function or class

---

Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog.

[lgtm-com]

This pull request fixes 1 alert when merging 613a3dc into 1dc42ba - view on LGTM.com

fixed alerts:

• 1 for Unused variable, import, function or class

---

Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog.

[lgtm-com]

This pull request fixes 1 alert when merging def0462 into e9fb32f - view on LGTM.com

fixed alerts:

• 1 for Unused variable, import, function or class

---

Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog.

[danielleadams]

@edwardfoyle you have some merge conflicts.

[lgtm-com]

This pull request fixes 1 alert when merging 4ac718e into b5a8783 - view on LGTM.com

fixed alerts:

• 1 for Unused variable, import, function or class

---

Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog.

[lgtm-com]

This pull request fixes 1 alert when merging 1be51ed into 7d17da9 - view on LGTM.com

fixed alerts:

• 1 for Unused variable, import, function or class

---

Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog.