Rename package #38
Description
This repo is evolving from "pretty formatter" to something more like "terminal formatters" that includes the pretty printer, progress printer and summary printer. This is a good direction! But it raises the question of whether we should rename the repo and the package(s) it publishes accordingly.
With JavaScript we have established a convention for message-based formatters where the default export from the package is the formatter plugin, meaning the package can be referenced directly like cucumber-js -f @cucumber/pretty-formatter (and shorthands like pretty are just an alias for this). We could maintain that by publishing a single npm package but using sub path exports so we'd have @cucumber/terminal-formatters/pretty and @cucumber/terminal-formatters/progress etc, and still do name exports on the main entry point for things that need to be accessed programatically or by type systems.