feat: add metrics metadata for auth mode and custom operations

[dpilch]

Description of changes

Add additional metrics metadata for authorizationMode and customOperations. The metric data is stored in the CFN stack description.

{
  "metadata": {
    "dataSources": "dynamodb,mysql,postgres", // exists today

    // new fields below
    /*
      Possible options
      'aws_iam',
      'openid_connect',
      'amazon_cognito_identity_pools',
      'amazon_congnito_user_pools',
      'api_key',
      'aws_lambda',
    */
    "authorizationModes", "api_key,aws_lambda",
    "customOperations": "queries,mutations"
  }
}

CDK / CloudFormation Parameters Changed

The metrics are stored in the CFN description. No real functional change, but the descriptions will be updated.

Issue #, if available

N/A

Description of how you validated changes

• Unit tests

Checklist

• PR description included
• yarn test passes
• Tests are changed or added

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

[palpatim]

This asserts order as well as content -- is that intentional?

[palpatim]

One of the tests above asserts the order of the auth mode metric. Is that intentional? Should we sort the values here so we can provide a stable value irrespective of the order in which they are declared?

[dpilch]

Good idea, I will apply a sort.

[palpatim]

Why not subscriptions?

[dpilch]

Wasn't in the product requirements, but we should probably just add it.

[palpatim]

As far as I can tell this is a typo in the PR description, but calling it out in case:

    /*
      Possible options
      'aws_iam',
      'openid_connect',
      'amazon_cognito_identity_pools',
      'amazon_congnit_user_pools',
      'api_key',
      'aws_lambda',
    */

[dpilch]

Yes, typo in the description. We can see amazon_congnito_user_pools is set correctly in the unit test.