Add support for Multi-AZ

[tmscarla]

Description

With ParallelCluster 3.4.0, customers are able to launch nodes across multiple availability zones, in order to increase capacity availability for their clusters.

This PR aims at adding support for Multi-AZ feature in ParallelCluster Manager.

If the deployed version of PC API is < 3.4.0, a single Select component is displayed in the subnet selection section in the Queues page. If PC API version >= 3.4.0 a MultiSelect component is displayed instead (see attached images). In this way, users are able to specify multiple subnets in different availability zones.

Changelog entry

• Added support for Multi-AZ

How Has This Been Tested?

• Unit tests
• Manual tests with 3.3.0 and 3.4.0 versions

References

• https://cloudscape.design/components/multiselect/
• https://cloudscape.design/get-started/testing/introduction/

PR Quality Checklist

• [x] I added tests to new or existing code
• [x] I removed hardcoded strings and used our i18n solution instead (see here)
• [ ] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
• [x] I checked that infrastructure/update_infrastructure.sh runs without any error
• [x] I checked that npm run build builds without any error
• [x] I checked that clusters are listed correctly
• [x] I checked that a new cluster can be created (config is produced and dry run passes)
• [ ] I checked that login and logout work as expected

In order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.