fix(apigateway): incorrect mapping of id in model schema definition

If we specify the `id` field when defining an Api Gateway Model's schema, it gets mapped to a `$id` key, which creates an invalid model because it doesn't comply with the DRAFT-04 specification. The specification requires this field to remain named as `id`.

fixes #14585

packages/@aws-cdk/aws-apigateway/lib/util.ts

@@ -95,7 +95,6 @@ export class JsonSchemaMapper {
   private static readonly SchemaPropsWithPrefix: { [key: string]: string } = {
     schema: '$schema',
     ref: '$ref',
-    id: '$id',
   };
   // The value indicates whether direct children should be key-mapped.
   private static readonly SchemaPropsWithUserDefinedChildren: { [key: string]: boolean } = {

packages/@aws-cdk/aws-apigateway/test/util.test.ts

@@ -1,5 +1,5 @@
 import '@aws-cdk/assert-internal/jest';
-import { JsonSchema, JsonSchemaType } from '../lib';
+import { JsonSchema, JsonSchemaType, JsonSchemaVersion } from '../lib';
 import { JsonSchemaMapper, parseAwsApiCall, parseMethodOptionsPath } from '../lib/util';
 
 describe('util', () => {
@@ -137,5 +137,18 @@ describe('util', () => {
         default: 'blue',
       });
     });
+
+    test('"id" maps to "id" when using DRAFT-04', () => {
+      const schema: JsonSchema = {
+        schema: JsonSchemaVersion.DRAFT4,
+        id: 'http://json-schema.org/draft-04/schema#',
+      };
+
+      const actual = JsonSchemaMapper.toCfnJsonSchema(schema);
+      expect(actual).toEqual({
+        $schema: 'http://json-schema.org/draft-04/schema#',
+        id: 'http://json-schema.org/draft-04/schema#',
+      });
+    });
   });
 });