Remove calls to process.exit()

[samayer12]

Describe what should be investigated or refactored

There are several spots where Pepr calls process.exit(). This complicates the ability to do global logging, auditing, or cleanup. We should avoid this pattern to handle failure cases in a more graceful manner. Consider this explanation for why it's a bad idea.

We'll know we're done with this issue when each of those calls to process.exit() handle shutdown in a more graceful manner (e.g., throwing exceptions, passing control to some other function, etc.)

Links to any relevant code

src/cli/build.ts:          process.exit(1);
src/cli/build.ts:            process.exit(1);
src/cli/build.ts:            process.exit(1);
src/cli/build.ts:          process.exit(1);
src/cli/build.ts:    process.exit(1);
src/cli/build.ts:    if (!e.stdout) process.exit(1); // Exit with a non-zero exit code on any other error
src/cli/deploy.ts:        process.exit(1);
src/cli/deploy.ts:        process.exit(1);
src/cli/deploy.ts:          process.exit(0);
src/cli/deploy.ts:          process.exit(1);
src/cli/dev.ts:          process.exit(0);
src/cli/dev.ts:            process.exit(1);
src/cli/dev.ts:        process.exit(1);
src/cli/format.ts:        process.exit(1);
src/cli/init/index.ts:          process.exit(1);
src/cli/kfc.ts:        process.exit(1);
src/cli/monitor.ts:        process.exit(1);
src/cli/update.ts:        process.exit(1);
src/cli/update.ts:        process.exit(1);
src/lib/assets/index.ts:      process.exit(1);
src/lib/assets/pods.ts:    process.exit(1);
src/lib/controller/index.ts:        process.exit(0);
src/lib/module.ts:          process.exit(1);
src/lib/watch-processor.ts:    process.exit(1);
src/lib/watch-processor.ts:    process.exit(1);
src/runtime/controller.ts:    process.exit(1);

Additional context

Generate the above list with the command grep "process.exit(" src/**/*.*s