fix: process input object, union and interface metadata in model introspection schema codegen

[AaronZyLee]

Description of changes

The input, union and interface types are correctly processed by the base visitor when it is defined in the GQL schema. The union and interface IR, however, will not be processed into the output of MIS

Codegen Parameters Changed or Added

The type of model schema is changed

export type ModelIntrospectionSchema = {
  version: 1;
  models: SchemaModels;
  nonModels: SchemaNonModels;
  enums: SchemaEnums;
  queries?: SchemaQueries;
  mutations?: SchemaMutations;
  subscriptions?: SchemaSubscriptions;
  // new root level optional attribute
  inputs?: SchemaInputs 
};

// New type definitions
export type SchemaInputs = Record<string, Input>;

export type Input = {
   name: string;
   arguments: Arguments
}

// Fine-grained field type
export type ScalarType = 'ID'
  | 'String'
  | 'Int'
  | 'Float'
  | 'AWSDate'
  | 'AWSTime'
  | 'AWSDateTime'
  | 'AWSTimestamp'
  | 'AWSEmail'
  | 'AWSURL'
  | 'AWSIPAddress'
  | 'Boolean'
  | 'AWSJSON'
  | 'AWSPhone';

export type InputFieldType = ScalarType
  | { enum: string }
  | { input: string };

export type FieldType = ScalarType
  | { enum: string }
  | { model: string }
  | { nonModel: string };

// Change argument field type
export Argument = {
  ...,
  type: InputFieldType
}

Input Example

Given the GraphQL schema in SDL

input CustomInput {
    customField1: String!
    customField2: BillingSource!
    customField3: NestedInput!
}
input NestedInput {
    content: String!
}
enum BillingSource {
    CLIENT
    PROJECT
}
type Query {
  echo(myInput: CustomInput): String!
}

The corresponding part will be generated in model introspection schema

{
    "queries": {
        "echo": {
            "name": "echo",
            "isArray": false,
            "type": "String",
            "isRequired": true,
            "arguments": {
                "myInput": {
                    "name": "myInput",
                    "isArray": false,
                    "type": {
                        "input": "CustomInput"
                    },
                    "isRequired": false
                }
            }
        }
    },
    "inputs": {
        "CustomInput": {
            "name": "CustomInput",
            "arguments": {
                "customField1": {
                    "name": "customField1",
                    "isArray": false,
                    "type": "String",
                    "isRequired": true
                },
                "customField2": {
                    "name": "customField2",
                    "isArray": false,
                    "type": {
                        "enum": "BillingSource"
                    },
                    "isRequired": true
                },
                "customField3": {
                    "name": "customField3",
                    "isArray": false,
                    "type": {
                        "input": "NestedInput"
                    },
                    "isRequired": true
                }
            }
        },
        "NestedInput": {
            "name": "NestedInput",
            "arguments": {
                "content": {
                    "name": "content",
                    "isArray": false,
                    "type": "String",
                    "isRequired": true
                }
            }
        }
    },
    "enums": {
        "BillingSource": {
            "name": "BillingSource",
            "values": [
                "CLIENT",
                "PROJECT"
            ]
        }
    },
}

Union & Interface

Union and Interface types will not be generated in the MIS json file. The fields with these types will be omitted when they present in type definition. They can still be recognized as it is being processed in the base visitor

Issue #, if available

Fix #794

Description of how you validated changes

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)
• Breaking changes to existing customers are released behind a feature flag or major version update
• Changes are tested using sample applications for all relevant platforms (iOS/android/flutter/Javascript) that use the feature added/modified
• Changes are tested on windows. Some Node functions (such as path) behave differently on windows.

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

[AaronZyLee]

This change responds to the opt-in regions used for e2e tests, which is similar to the related cleanup script change in API category

[iartemiev]

Granting admin approval after reviewing API.md and .codebuild/* changes. Did not review implementation changes.