Disable Cost Monitoring in unsupported regions

[tmscarla]

Description

Due to an issue with ParallelCluster UI 2023.05, deployment of PCUI in GovCloud west region fails with a Cloudformation error message. The issue is rooted in the fact that the Cost monitoring feature is not supported in GovCloud west region and trying to activate it will result in an error.

We have already provided a mitigation for our customers, which will enable them to deploy PCUI in GovCloud region.

The mitigation has some drawbacks: a list of API calls errors will appear on the PCUI console when performing cluster operations. This is due to the fact cost monitoring API calls are still performed in a region which does not support cost monitoring.

This PR solves the aforementioned issue by introducing a mechanism in featureFlagsProvider to disable a feature if not supported in a specific region.

Closes https://github.com/aws/aws-parallelcluster-ui/issues/236.

How Has This Been Tested?

• Unit tests
• Manual tests targeting demo environment with local changes (could not directly test deployment in us-gov-west-1)
  • If eu-west-1 is marked as not supported for cost_monitoring feature, no API calls is made to /cost-monitoring endpoint neither the tab is shown in cluster details page.
  • Viceversa, if eu-west-1 is supported for cost_monitoring feature API calls are executed successfully and the 'Cost monitoring' tab is shown as expected

References

• https://github.com/aws/aws-parallelcluster-ui/issues/236
• https://github.com/aws/aws-parallelcluster-ui/issues/213

PR Quality Checklist

• [x] I added tests to new or existing code
• [ ] I removed hardcoded strings and used react-i18next library (useTranslation hook and/or Trans component), see an example 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 made sure that any GitHub issue solved by this PR is correctly linked
• [ ] 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)
• [x] 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.