Update AwsAuthManager to support multi-team #65371

[haseebmalik18]

AwsAuthManager currently ignores team_name entirely and is_authorized_team raises NotImplementedError, which blocks multi-team for AWS deployments.

Following the KeycloakAuthManager as reference, this PR:

• Extracts team_name from resource details in is_authorized_* methods
• Implements is_authorized_team with a new TEAM AVP entity
• Passes team_name through filter_authorized_* methods to the AVP facade
• Enhances AVP context with team_name for Cedar policy evaluation
• Updates the Cedar schema with Team entity type and team_name context on team-scoped actions

closes: #65371

[vincbeck]

Did you actually tested it with your AWS account?

[haseebmalik18]

Hey, I tested this against a real Amazon Verified Permissions policy store and everything works as expected. The updated schema uploads fine, Cedar policies can use context.team_name to scope access by team, and the new Team entity type works for membership checks. Verified all the ALLOW/DENY scenarios through the Test Bench

[vincbeck]

Thank you!