Consider reducing config clutter?

[jcbhmr]

Having dist in source control is ok (if a little distasteful, but I digress) but there's a lot of clutter here! 🤮 I think we should reduce the clutter! 😁

Some ideas:

• Use Node.js' new node:test and node --test builtin test runner https://nodejs.org/api/test.html (removes jest config) or use https://vitest.dev/ which supports TS out of the box (zero-config)
• remove dist from source control so that you can prettier --ignore-path .gitignore
• move prettierrc to prettier: {} in package.json
• put contributors in a <details> dropdown at the bottom of the readme? (removes CREDITS.md) (https://allcontributors.org/docs/en/bot/installation#3-create-a-readmemd)
• remove .editorconfig and rely on running prettier -w . to even things out? Relying on CLI tools is the lowest common denominator; even VS Code needs an extension

Of those, I think these are the most feasible (easy)

• prettierrc ➡ package.json
• CREDITS.md ➡ README.md <details>
• jest ➡ vitest/node:test

[spenserblack]

Having dist in source control is ok

Borders on required for any Node.js action if you want to allow users to use it from @main, since AFAIK each action is checked out from the specified ref.

---

• Moving prettier config to package.json "unclutters" file tree by cluttering package.json, right? 😉
• I'm going to need a better argument for switching testing tools than "we can remove a config file"