Improve error reporting and handling by providing a mechanism for logs to be remotely captured

Currently all printer client logs are written to the terminal window that the printer client launches in. This makes debugging printer problems very difficult, as it relies on the card office staff screenshotting or C&Ping the terminal output over to us. To improve this we should investigate having the logs sent to a remote location that can be easily accessed by developers.

Acceptance Criteria

• Printer client stdout is logged to a standard location, easily accessible by all Wilson team developers.

added issuetypeTask meetingbacklog refinement priority3 Low teamIdentity labels

added to epic uis/devops/iam&117

We could in theory tie this to the front end requirements as well and see if there's a common platform we can use.

We could also in theory create an API in the API GW that spits messages straight into gcp logs...

I was also thinking a logging API might be useful, possibly will be applicable for lots of other things that we need to understand but don't live in GCP world. May also be worth checking if (for example) Digital Admissions have a solution for logging on their frontend, as they're definitely ahead of us in terms of frontend tech.

added communal-benefit label