[Resource Type] - [Enhancement] - Removing authorizer from `AWS::ApiGatewayV2::Route` requires setting `AuthorizerId` to `"NONE"`"

### Name of the resource

AWS::ApiGatewayV2::Route

### Resource name

_No response_

### Description

Removing an existing authorizer from an `AWS::ApiGatewayV2::Route` does not work by just removing the `AuthorizationType` and `AuthorizerId`. When doing that the CloudFormation or CloudControl operations are successful, but the existing authorizer stays attached to the route.

Instead, users need to remove the `AuthorizerId` and set `AuthorizationType` to `"NONE"`.

### Other Details

Users across different ecosystems seem to be running into this:
- https://github.com/pulumi/pulumi-aws-native/issues/1822
- https://github.com/aws/aws-cdk/issues/20695

Start by reviewing the reported AWS::ApiGatewayV2::Route behavior for CloudFormation and CloudControl operations, then compare the linked Pulumi and AWS CDK reports. Determine how authorizer removal is expected to work when AuthorizationType and AuthorizerId are changed, and document or validate the resulting coverage-roadmap requirement.

Written by the indexing model from the issue text.