feat(core, prompts): add async autocomplete options

[mateussilva92]

This PR enhances the autocomplete prompt to support async option functions.

Fixes:

#467

What’s New:

Autocomplete:

• Autocomplete options can now be provided as an async function;
• Request cancellation via AbortController;
• Stale responses are safely ignored to prevent race conditions;
• Proper loading state handling;

Common/Helper:

• unicodeOr is now generic
• isAsync function was added.

Backwards Compatibility:

• Existing sync configurations continue to work unchanged.
• No existing unit tests changed.

Notes:

This PR has the feature itself fully developed. I didn't create any unit tests yet since I want to get feedback on my implementation. When I get an thumbs up on the implementation I'll add the unit tests / examples and remaining files.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c531b6b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

• @example/basic

• @example/changesets

  npm i https://pkg.pr.new/@clack/core@471
  

  npm i https://pkg.pr.new/@clack/prompts@471
  

commit: ebd1852

[43081j]

this is a very large change for something we haven't seen much demand for. also note that this doesn't fix #467, it just adds async on top of what that is asking to document.

i very much appreciate the work that has gone into this, but am tempted to leave it sync-only until we see some real demand for it. otherwise it is a slippery slope to introducing a lot of extra code for edge case features.

@dreyfus92 thoughts?

[dreyfus92]

i agree. i'd rather keep it as it is until we see a real demand, this is a lot of surface for an edge case. a couple of things for context: #467 is asing for a reordering filter, not async, and that's already doable with the options getter reading this.userInput. so the fix there is docs, happy to review a pr for that.