chore(cli): Telemetry robustness and command name convention

[Josh-Walker-GM]

WIP

Changes

1. Makes the OTel telemetry more robust:
   • Shutdown is now a sync function so can be directly included within the process.on('exit', ...) event. This ensures telemetry is always shutdown
   • Fixes to some incorrect file IO
   • More error handling within the telemetry sending process to prevent loops of errors
2. Command names recorded by telemetry are all now just given directly as hard coded strings. Just adopting one way of doing it so we're consistent and clear.
   • Prevents inadvertent command names reported to telemetry which contain the yargs positional argument declarations. E.g. cell vs cell <name>

Minor changes
I'm happy to revert the following changes if they're contentious:

1. Helper function to exit with an error lib/exit.js: exitWithError. This ensures consistent output styling and consistency in functionality such as setting the exit code.
   • This is more UX and so we'll like iterate on this.
2. Included example use of this exitWithError within devHandler.js. Minimal usage which occurs only on port collisions.

Pushed

1. Removing all the handler level try/catch where they are no longer needed.
   • Let's have a separate PR for that
2. Implementing exitWithError where it would be appropriate.
   • More UX, deserves discussion and iteration, best for a separate PR