fix(cli): improve fuzzy search in selectors and completions

[betegon]

Follow-up to #1495: use mode: "search" for selectors and autocomplete.

The same matcher serves two cases:

• resolving names in submitted commands
• suggesting candidates while typing.

"search" mode separates their matching rules.

Short queries match literal text only; longer queries tolerate typos in unfinished prefixes.

fuzzyMatch("zz", ["UI"], { mode: "search" }); // []
fuzzyMatch("frone", ["frontend-web"], { mode: "search" }); // ["frontend-web"]
fuzzyMatch("frone", ["frontend-web"]); // [] — submitted-command behavior stays unchanged

Selectors let users choose a candidate. Command recovery automatically uses a sole match, with a warning. Applying search rules globally would therefore change which project a command uses, or make an existing recovery ambiguous:

const projects = ["sentry", "sentry-relay"];
fuzzyMatch("senry", projects); // ["sentry"]
fuzzyMatch("senry", projects, { mode: "search" }); // ["sentry", "sentry-relay"]

The mode keeps these policies separate while reusing the same matcher. Regression tests cover both search behavior and unchanged command resolution.