Support AutoName for Plugin Framework based resources

[t0yv0]

This is on top of pulumi/pulumi-terraform-bridge#1321

Fixes #2644

Auto-naming is now supported for PF so besides fixing the warning for requested resources it rolls it out to all of these:

• resource:aws_appconfig_environment
• resource:aws_auditmanager_assessment
• resource:aws_auditmanager_assessment_report
• resource:aws_auditmanager_control
• resource:aws_auditmanager_framework
• resource:aws_cognito_user_pool_client
• resource:aws_opensearchserverless_access_policy
• resource:aws_opensearchserverless_collection
• resource:aws_opensearchserverless_security_config
• resource:aws_opensearchserverless_security_policy
• resource:aws_opensearchserverless_vpc_endpoint
• resource:aws_quicksight_vpc_connection
• resource:aws_resourceexplorer2_view
• resource:aws_route53_cidr_collection
• resource:aws_route53_cidr_location
• resource:aws_simpledb_domain

TODOs:

• release underlying bridge support
• verify end to end on one of these resources
• rebuild schema and SDKs

[t0yv0]

Verified on aws:route53/cidrCollection:CidrCollection

[iwahbe]

Two nits, but otherwise looks good.

[t0yv0]

command.go:83: Invoke '/opt/hostedtoolcache/pulumi/3.76.1/x64/pulumi login --cloud-url https://api.pulumi-staging.io/' failed: exit status 255
  Logging in using access token from PULUMI_ACCESS_TOKEN
  error: problem logging in: invalid access token

Hmm, is this a flake or something more serious? Trying again.

[t0yv0]

No it's persistent. Will investigate tomorrow.

[iwahbe]

@t0yv0 Could this be related to https://pulumi.slack.com/archives/CBUP505U7/p1691101512583479?

[iwahbe]

LGTM

[mikhailshilkov]

Indeed, I think the test failures were for an unrelated reason (org tokens). I reran and it's green now.

[t0yv0]

thank you!