fix: throws error if a sub-argument is incorrect/not-supported

[igoyalsamarth]

Description

Throws error if a sub-argument is incorrect/not-supported. Also suggests possible sub-arguments of the same type that the dev was probably confused with.

test-folder % vitest --coverage.thresholds.invalidThreshold 100

Error: Unknown option "coverage.thresholds.invalidThreshold". Did you mean one of: "coverage.thresholds.100", "coverage.thresholds.perFile", "coverage.thresholds.autoUpdate", "coverage.thresholds.lines", "coverage.thresholds.functions", "coverage.thresholds.branches", "coverage.thresholds.statements"? Use '--help --coverage' for more info.

Resolves #9056

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.
• Please check Allow edits by maintainers to make review process faster. Note that this option is not available for repositories that are owned by Github organizations.

Tests

• Run the tests with pnpm test:ci.

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.