feat: autocomplete choices for options

[ansgarm]

Hi!

This PR introduces support for auto completing choices if an option has been specified which has choices but no value has been selected yet. For example:

> cdktf convert --language <TAB>
csharp      java        python      typescript

when the option has been specified like this: (source)

.option("language", {
  choices: ["typescript", "python", "csharp", "java"],
  default: "typescript",
})

Background

We use yargs for the CDK for Terraform and wanted to introduce support for shell completion. As we wanted to offer support for auto completing choices for options, I figured I'd do a PR instead of building a custom completion handler in multiple places.

If there's anything I can do to get this merged, please tell me!

P.S. It also fixes #2016 because that caused the build to fail for me and there's no package-lock.json or alike.

[bcoe]

This seems like a great addition to completion functionality 👍 and I appreciate the fix for TypeScript.

[rvitaliy]

👋 hi all, here my 50cent, sorry!

The scope of usage unknown instead of any is to prevent fatal errors when catch receive something what is not an Error.

"errorString".stack > fatal error
to avoid this i suggest to add a check if err is instance of Error like suggested by documentation instead of cast err as Error

https://devblogs.microsoft.com/typescript/announcing-typescript-4-4/#use-unknown-catch-variables