Fixing issue 949: validate consumer roles

[SofiaSazonova]

Feature or Bugfix

• Bugfix

Detail

Check if role ARN matches the role name (boto3 get_role works by name, not by arn)

Relates

#949

Security

• Does this PR introduce or modify any input fields or queries - this includes
  fetching data from storage outside the application (e.g. a database, an S3 bucket)? N/A
  • Is the input sanitized?
  • What precautions are you taking before deserializing the data you consume?
  • Is injection prevented by parametrizing queries?
  • Have you ensured no eval or similar functions are used?
• Does this PR introduce any functionality or component that requires authorization?N/A
  • How have you ensured it respects the existing AuthN/AuthZ mechanisms?N/A
  • Are you logging failed auth attempts?N/A
• Are you using or adding any cryptographic features?N/A
  • Do you use a standard proven implementations?N/A
  • Are the used keys controlled by the customer? Where are they stored?N/A
• Are you introducing any new policies/roles/users?N/A
  • Have you used the least-privilege principle? How?N/A

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

[noah-paige]

Tested this PR in AWS Deployment, validated:

• CICD Pipeline Succeeds
• Add Consumption Role Fails - Wrong Role Name
• Add Consumption Role Fails - Wrong Account ARN
• Add Consumption Role Succeeds - Correct Role ARN
• Remove Consumption Role Succeeds

Will wait until npm-audit check is fixed in separate PR before then approving and merging this one as well

[noah-paige]

@SofiaSazonova - could you merge latest OS to your branch? I can approve once confirm npm-audit check successful

[SofiaSazonova]

Done

[noah-paige]

looks good! Approving