feat(openapi): add update option to automatically update an only available spec file without any prompts

[shaiarmis]

Today when using the rdme openapi <path> --version=<version> command to update a spec file (selecting Update in the first prompt), we're prompted for selecting an API spec file, even if there's only a single one present.

🧰 Changes

This PR adds the --updateSingleSpec option that will instruct the CLI to not prompt the user if there's only a single spec file available, and choose it automatically.

🧬 QA & Testing

1. Start with a clean project with no API spec files at all
2. Run rdme openapi <path> --version=<version>, which will upload the file without any create/update prompt because there's nothing to update.
3. Run rdme openapi <path> --version=<version> once again, and select update in the first prompt and expect to see another prompt with a single option.
4. Abort the previous command.
5. Run rdme openapi <path> --version=<version> --updateSingleSpec and expect the file to upload successfully without any prompts.

[domharrington]

Thanks for this! I'm gunna assign to @kanadgupta as he's the person primarily responsible for managing this repo. I think we already have some things in the works to help with this, but i'll see what Kanad says.

[kanadgupta]

Thanks for the PR! Can you add two pieces of logic (and corresponding test cases):

• An error message if a user passes this --updateSingleSpec flag but apiSettingsBody.length is greater than 1
• A warning output if a user passes in the --id parameter AND the --updateSingleSpec flag (similar to this)

[kanadgupta]

Also—please ignore the failing GitHub Action Dry Run step since that's a known issue with external contributors—but if you could fix the failing snapshots in the Test Suite, that'd be great. Thank you!

[shaiarmis]

Also—please ignore the failing GitHub Action Dry Run step since that's a known issue with external contributors—but if you could fix the failing snapshots in the Test Suite, that'd be great. Thank you!

Done

[shaiarmis]

Thanks for the PR! Can you add two pieces of logic (and corresponding test cases):

• An error message if a user passes this --updateSingleSpec flag but apiSettingsBody.length is greater than 1
• A warning output if a user passes in the --id parameter AND the --updateSingleSpec flag (similar to this)

Done x 2

[erunion]

thanks for this!

[erunion]

Suggested change

	'When using the `--id` option the `--updateSingleSpec` option is ignored, as the desired spec id is already specified.'
	'When using the `--id` option the `--updateSingleSpec` option is ignored as the desired spec is already specified.'

[kanadgupta]

Made a few copy edits and added a tiny error case. Thanks again for the PR @shaiarmis!

[shaiarmis]

@kanadgupta thanks for the additional changes, they make a lot of sense :)
Should I wait for @erunion's approval before merging this PR?

[shaiarmis]

LOL just realized I don't have permissions to merge ^_^ So go ahead and merge at your leisure.