chore: migrate from chalk to stdlib

[SethFalco]

Description

I recently learned that Node.js v20/v21 introduces a simple style API for doing things like color in the terminal. That can replace libraries like chalk, yoctacolor, picocolor, etc.

This doesn't make those other libraries redundant, some of them have their own perks. However, for an application like this, I think using the standard library would be better suited.

As this project already requires Node.js v22 or higher, it should be perfectly safe to use in that regard.

⚠️ Breaking Change

There is a minor difference in config between chalk and the standard library.

Namely:

• chalk uses overline while stdlib uses overlined
• chalk has a visible option while stdlib has no such option

I believe the API's overlap in regarding all other properties. We could preserve the backward compatibility more fully by adding our own aliases for these, but I'm not sure if it's worthwhile.

Not Breaking Change

Actually, this is not a breaking change. I see in the code that we hardcoded a list of valid values for the theme, which do not include visible or overline/overlined anyway. As those are the only differences in terms of keywords, I believe this should be backward compatible. 🎉

Checklist

Please review this checklist before submitting a pull request.

• Code compiles correctly
• Created tests, if possible
• All tests passing (npm run test:all)
• Extended the README / documentation, if necessary

Related

• Closes build(deps): bump chalk from 4.1.2 to 5.6.2 #509 (No need to upgrade chalk in our package.json if it's no longer present there.)