Update modules for v9

[jsumners]

To prepare for v9 we need to go through the list of repositories in this issue and:

1. Determine if the module should be archived and marked as deprecated. Mostly we should look at the commit history to determine if the community is interested in the module. A secondary check would be inspecting the data for the module at npm-stat.com. Unless we have people using, and contributing, to modules, we should be reducing our maintenance burden by archiving them.
2. Evaluate if the module needs any updates. Most likely this will simply mean updating dependencies, dropping Node <= 16, and updating CI configuration accordingly. It would be nice to get the testing suite (tap) configured the same as in the core repo, and any Coveralls usage removed, but this is not necessary for release.

If you are able to help with any of these, please create a new issue in the repo you're interested in that has the title "Updating for v9" and a body with something like "👋 I'm X, and would like to work on this." It should also include a link back to this issue. After that issue is created, either I (@jsumners) or @mcollina will create a next branch for you to target. Once that branch is created, you will be able to start a new Pull Request that targets it. We will help out with any questions you may have.

---

• json-colorizer
• koa-pino-logger
• pino-abstract-transport
• pino-arborsculpture
• pino-caller
• pino-clf
• pino-debug
• pino-elasticsearch
• pino-eventhub
• pino-filter
• pino-gelf
• pino-http
• pino-http-print
• pino-integration
• pino-mongodb
• pino-nextjs-example
• pino-noir
• pino-pretty
• pino-sapling
• pino-socket
• pino-std-serializers
• pino-syslog
• pino-tee
• pino-toke
• pino-webpack-plugin
• pinojs
• quick-format-unescaped
• real-require
• restify-pino-logger
• rill-pino-logger
• sonic-boom
• thread-stream