Registrar silently crashes at bootup

[CharlieC3]

At bootup, if the registrar cannot reach an API instance at https://stacks-node-api.stacks.co/v2/info, it'll log an error and fail to complete startup. It will also fail to gracefully exit.

registrar

@promster/server started on port 9153.
{"message":"Error fetching block height. request to https://stacks-node-api.stacks.co/v2/info failed, reason: connect ETIMEDOUT 104.22.42.120:443","stack":"Error: Error fetching block height. request to https://stacks-node-api.stacks.co/v2/info failed, reason: connect ETIMEDOUT 104.22.42.120:443\n    at updateGlobalBlockHeight (/src/subdomain-registrar/lib/operations.js:2901:11)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)","level":"error","timestamp":"2022-08-27T00:36:53.151Z"}
{"level":"error","message":"Error: Error fetching block height. request to https://stacks-node-api.stacks.co/v2/info failed, reason: connect ETIMEDOUT 104.22.42.120:443\n    at updateGlobalBlockHeight (/src/subdomain-registrar/lib/operations.js:2901:11)\n    at processTicksAndRejections (internal/process/task_queues.js:97:5)","timestamp":"2022-08-27T00:36:53.152Z"}       (node:9) UnhandledPromiseRejectionWarning: Error: Error fetching block height. request to https://stacks-node-api.stacks.co/v2/info failed, reason: connect ETIMEDOUT 104.22.42.120:443        at updateGlobalBlockHeight (/src/subdomain-registrar/lib/operations.js:2901:11)                                                                                                            at processTicksAndRejections (internal/process/task_queues.js:97:5)                                                                                                                    (node:9) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)                                                                                                                                         (node:9) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

If this were to happen, ideally the registrar would retry indefinitely and finish the startup process.