[FEATURE] Add support to deploy multiple AWS Config Conformance Packs

**Community Note**

- Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment

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

We have a use case where we need to deploy more than one Config Conformance Packs, such as HIPAA and FFIEC. However, SRA solution only supports deploying one Conformance Pack at this time.

This limitation requires us to deploy and manage the second Conformance Pack out of the SRA solutions, which is not ideal.

### Describe the solution you'd like

It'd be great if SRA could support more than one Conformance Packs. Some parameter that prompts the user for the number of Conformance Packs to deploy and then gets the names of multiple Conformance Packs as a comma separated values. Just a thought.

### Describe alternatives you've considered

For now, we are deploying and managing the multiple Conformance Packs directly via CloudFormation, outside of SRA.

### Additional context

N/A

No file or test is named in the issue, so start by locating the SRA CloudFormation definition and parameters for the currently supported AWS Config Conformance Pack. Trace how the existing pack is deployed, then determine the scope needed for multiple pack names; done means SRA can deploy and manage more than one pack instead of requiring separate CloudFormation resources.

Written by the indexing model from the issue text.