Feat(@inquirer/core): Pass status to `usePrefix`/`theme.message` + Change default prefix

[nvlang]

This PR includes 5 commits:

• 82778c12a30755e87c1f1c6c42014199d313dc92 — Add .DS_Store to .gitignore for better DX on macOS
• 6eb53814aa7ad47f85ac811ee8ff6a47594c36b7 — Pass status to usePrefix (instead of isLoading). Also updates references to isLoading in README. This allows for behavior like the one described in #1537 to be implemented by the user.
• eced5d67b7229dbac760a48544c211b5626b11c0 — Pass status to style.message function as a second argument. This allows for behavior like the one described in https://github.com/SBoudrias/Inquirer.js/issues/1537#issuecomment-2336762834 to be implemented by the user.
• cc87d136685b9877afa50df313e7bd8cbcb881ad — Add TSDocs for Theme type (via local DefaultTheme type). This should improve IntelliSense.
• bf0e8ea61355dfd7935a98857f09c7bde6718c11 — Modify a unit test to test that the status property passed to usePrefix works as expected.

What's missing is a unit test for the changes to style.message. However, I couldn't immediately find unit tests for style.message to use as a template, and I didn't want to write one from scratch, since I'm not familiar with the setup. I tested the new style.message functionality locally via corepack yarn demo, and there it seemed to work fine.

Closes #1537.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@d2690cc). Learn more about missing BASE report.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1544 +/- ## ======================================= Coverage ? 97.78% ======================================= Files ? 39 Lines ? 2391 Branches ? 644 ======================================= Hits ? 2338 Misses ? 46 Partials ? 7 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[nvlang]

I think ? for when the question is pending and ✔ for when it's done could make sense? And maybe making the question mark blue and the checkmark green? I had left it alone since it seemed like it'd be a matter of personal preference, but I'd be glad to try to add whatever default you'd prefer.

Also, I wholeheartedly agree about giving status specific allowed strings — if I recall correctly, I had seen 'pending', 'loading', and 'done' being used, but also 'idle' in a unit test somewhere. I assume the first three should suffice, or would it make sense to include more statuses in your opinion?

[SBoudrias]

1. Prefix, yeah blue/green question mark/check mark sounds good to me.

2. I think we can go with 3 status. I prefer idle to pending; so I'd normalize this way. (maybe you'll find a valid 4th one when running typecheck, so low risk of missing one.)

[nvlang]

@SBoudrias I guess changing the default prefix means that we should also update the screenshots in the READMEs — however, I'm not sure what the setup / workflow there is (theme, font, etc.).

[SBoudrias]

Thanks for the work you've put on that PR!

I went ahead a made a few adjustments before merging (just an FYI):

• Used @inquirer/figures for the tick; since I don't think there was a fallback on windows.
• Replaced the interface of prefix from a function to a record.
• Updated documentation.

[SBoudrias]

About the screenshots, they were first introduced in #625... Feel free to regenerate screenshot and document a reproducible process in the CONTRIBUTING.md doc! (not sure if the same will work out of the box today 😬 - it's from 2018)