flowforge-nr-launcher missing try/catch on http request

[hardillb]

Current Behavior

FlowFuse/docker-compose#45

If api_url is wrong (or forge app is down) the the got request to get settings will fail and crash with hard to decipher stacktrace

Expected Behavior

Catch the error and log suitable message.

Probably exit nr-launcher cleanly (localfs and k8s drivers will automatically try and restart after suitable backoff time, need to check docker)

Steps To Reproduce

In docker-compose etc/flowforge.yml change the api_url

Environment

• FlowForge version: 0.10.0
• Node.js version: 16.x
• npm version: 8.x
• Platform/OS: docker
• Browser: na

[Steve-Mcl]

verified on local only.
killing forge app does not cause exception in launcher.

[Steve-Mcl]

@knolleary @hardillb not sure we can test this on staging?
Should we consider this fairly innocuous PR "done"?

[knolleary]

Yes

[hardillb]

Ship it, you need to set a bad api_url which I can't remember if localfs uses

I will break a docker build when I feel better