chore(cli): CliArguments interface generated from config.ts (aws#32556

)

This PR: 

- generates a new type, `CliArguments` which is an interface created from the cli source-of-truth in `config.ts`.
- renames `yargs-gen` into `cli-args-gen` to better reflect what we are generating now

The purpose of `CliArguments` is to eventually replace our current `Arguments` type, turning it into a strongly-typed object. `Arguments` today looks like this:

```ts
export type Arguments = {
  readonly _: [Command, ...string[]];
  readonly exclusively?: boolean;
  readonly STACKS?: string[];
  readonly lookups?: boolean;
  readonly [name: string]: unknown;
};
```

And because the last line in the definition essentially accepts any kind of property, we end up passing in and using values that are not documented anywhere. The purpose of this PR is to introduce a better type to enforce that the `args` object in `cli.ts` only holds values we expect. We are not currently using the new type anywhere; that will be done in a subsequent PR. 

The success criteria of this PR is that we are generating a new type from the source of truth that will eventually represent the type of the object we receive from CLI inputs.

Part of aws#32474 


### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

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

aws-cdk.code-workspace

@@ -31,7 +31,7 @@
         "name": "aws-custom-resource-sdk-adapter",
         "rootPath": "packages/@aws-cdk/aws-custom-resource-sdk-adapter"
       },
-      { "name": "yargs-gen", "rootPath": "tools/@aws-cdk/yargs-gen" }
+      { "name": "cli-args-gen", "rootPath": "tools/@aws-cdk/cli-args-gen" }
     ]
   },
   "extensions": {

codecov.yml

@@ -30,3 +30,7 @@ component_management:
       name: packages/aws-cdk # display name that can change freely
       paths:
         - packages/aws-cdk/**
+
+# https://docs.codecov.com/docs/ignoring-paths
+ignore:
+  - packages/aws-cdk/lib/parse-command-line-arguments.ts # this file is generated and some lines cannot be tested

lerna.json

@@ -10,7 +10,7 @@
     "packages/@aws-cdk-testing/*",
     "packages/@aws-cdk/*/lambda-packages/*",
     "tools/@aws-cdk/cdk-build-tools",
-    "tools/@aws-cdk/yargs-gen",
+    "tools/@aws-cdk/cli-args-gen",
     "tools/@aws-cdk/cdk-release",
     "tools/@aws-cdk/node-bundle",
     "tools/@aws-cdk/pkglint",

package.json

@@ -77,7 +77,7 @@
       "packages/@aws-cdk-testing/*",
       "packages/@aws-cdk/*/lambda-packages/*",
       "tools/@aws-cdk/cdk-build-tools",
-      "tools/@aws-cdk/yargs-gen",
+      "tools/@aws-cdk/cli-args-gen",
       "tools/@aws-cdk/cdk-release",
       "tools/@aws-cdk/node-bundle",
       "tools/@aws-cdk/pkglint",

packages/aws-cdk/CONTRIBUTING.md

@@ -1,21 +1,21 @@
 ## CLI Commands
 
 All CDK CLI Commands are defined in `lib/config.ts`. This file is translated
-into a valid `yargs` configuration by `bin/yargs-gen`, which is generated by `@aws-cdk/yargs-gen`.
+into a valid `yargs` configuration by `bin/cli-args-gen`, which is generated by `@aws-cdk/cli-args-gen`.
 The `yargs` configuration is generated into the function `parseCommandLineArguments()`,
 in `lib/parse-command-line-arguments.ts`, and is checked into git for readability and
 inspectability; do not edit this file by hand, as every subsequent `yarn build` will
 overwrite any manual edits. If you need to leverage a `yargs` feature not used by
-the CLI, you must add support for it to `@aws-cdk/yargs-gen`.
+the CLI, you must add support for it to `@aws-cdk/cli-args-gen`.
 
-Note that `bin/yargs-gen` is executed by `ts-node`, which allows `config.ts` to
+Note that `bin/cli-args-gen` is executed by `ts-node`, which allows `config.ts` to
 reference functions and other identifiers defined in the CLI before the CLI is
 built.
 
 ### Dynamic Values
 
 Some values, such as the user's platform, cannot be computed at build time.
-Some commands depend on these values, and thus `yargs-gen` must generate the
+Some commands depend on these values, and thus `cli-args-gen` must generate the
 code to compute these values at build time.
 
 The only way to do this today is to reference a parameter with `DynamicValue.fromParameter`.