docs(core): update FEATURE_FLAGS.md (#27269)

FEATURE_FLAGS.md is not updated so updated it with rebuild.

----

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

packages/@aws-cdk/cx-api/FEATURE_FLAGS.md

@@ -59,6 +59,8 @@ Flags come in three types:
 | [@aws-cdk/aws-efs:denyAnonymousAccess](#aws-cdkaws-efsdenyanonymousaccess) | EFS denies anonymous clients accesses | 2.93.0 | (default) |
 | [@aws-cdk/aws-efs:mountTargetOrderInsensitiveLogicalId](#aws-cdkaws-efsmounttargetorderinsensitivelogicalid) | When enabled, mount targets will have a stable logicalId that is linked to the associated subnet. | 2.93.0 | (fix) |
 | [@aws-cdk/aws-lambda-nodejs:useLatestRuntimeVersion](#aws-cdkaws-lambda-nodejsuselatestruntimeversion) | Enables aws-lambda-nodejs.Function to use the latest available NodeJs runtime as the default | 2.93.0 | (default) |
+| [@aws-cdk/aws-appsync:useArnForSourceApiAssociationIdentifier](#aws-cdkaws-appsyncusearnforsourceapiassociationidentifier) | When enabled, will always use the arn for identifiers for CfnSourceApiAssociation in the GraphqlApi construct rather than id. | 2.97.0 | (fix) |
+| [@aws-cdk/aws-rds:auroraClusterChangeScopeOfInstanceParameterGroupWithEachParameters](#aws-cdkaws-rdsauroraclusterchangescopeofinstanceparametergroupwitheachparameters) | When enabled, a scope of InstanceParameterGroup for AuroraClusterInstance with each parameters will change. | 2.97.0 | (fix) |
 
 <!-- END table -->
 
@@ -108,7 +110,9 @@ The following json shows the current recommended set of flags, as `cdk init` wou
  "@aws-cdk/aws-efs:denyAnonymousAccess": true,
  "@aws-cdk/aws-opensearchservice:enableOpensearchMultiAzWithStandby": true,
  "@aws-cdk/aws-lambda-nodejs:useLatestRuntimeVersion": true,
- "@aws-cdk/aws-efs:mountTargetOrderInsensitiveLogicalId": true
+ "@aws-cdk/aws-efs:mountTargetOrderInsensitiveLogicalId": true,
+ "@aws-cdk/aws-rds:auroraClusterChangeScopeOfInstanceParameterGroupWithEachParameters": true,
+ "@aws-cdk/aws-appsync:useArnForSourceApiAssociationIdentifier": true
  }
 }
 ```
@@ -1113,4 +1117,37 @@ shipped as part of the runtime environment.
 **Compatibility with old behavior:** Pass `runtime: lambda.Runtime.NODEJS_16_X` to `Function` construct to restore the previous behavior.
 
 
+### @aws-cdk/aws-appsync:useArnForSourceApiAssociationIdentifier
+
+*When enabled, will always use the arn for identifiers for CfnSourceApiAssociation in the GraphqlApi construct rather than id.* (fix)
+
+When this feature flag is enabled, we use the IGraphqlApi ARN rather than ID when creating or updating CfnSourceApiAssociation in 
+the GraphqlApi construct. Using the ARN allows the association to support an association with a source api or merged api in another account.
+Note that for existing source api associations created with this flag disabled, enabling the flag will lead to a resource replacement.
+
+
+| Since | Default | Recommended |
+| ----- | ----- | ----- |
+| (not in v1) | | |
+| 2.97.0 | `false` | `true` |
+
+
+### @aws-cdk/aws-rds:auroraClusterChangeScopeOfInstanceParameterGroupWithEachParameters
+
+*When enabled, a scope of InstanceParameterGroup for AuroraClusterInstance with each parameters will change.* (fix)
+
+When this feature flag is enabled, a scope of `InstanceParameterGroup` for
+`AuroraClusterInstance` with each parameters will change to AuroraClusterInstance
+from AuroraCluster.
+
+If the flag is set to false then it can only make one `AuroraClusterInstance`
+with each `InstanceParameterGroup` in the AuroraCluster.
+
+
+| Since | Default | Recommended |
+| ----- | ----- | ----- |
+| (not in v1) | | |
+| 2.97.0 | `false` | `true` |
+
+
 <!-- END details -->