User story
As a developer (ay6), I would like sprint client response to be handled in Limber to show correct and useful feedback for label printing using squix printers.

print_to_sprint method of PrintJob class does not handle the response code and body and returns success even if there are errors. The view always shows info about sending of print requests to the printer as success even though requests do not reach the printer or labels are not printed.

Who are the primary contacts for this story
kt17
ay6
as28

Who is the nominated tester for UAT
TBD

Acceptance criteria
To be considered successful the solution must allow:

• response object returned by SPrintClient.send_print_request call is checked, for status and message body.
• On failure, useful feedback is added for the view using errors.add and false is returned for PrintJobsController
• Preferably, print job id in response from sprint is used for finding out the actual status of printing.

Dependencies
This story is blocked by the following dependencies:

• #<issue_no.>
• sanger/#<issue_no.>

References
This story has a non-blocking relationship with:

• #<issue_no.>
• sanger/#<issue_no.>

Additional context

• See https://ruby-doc.org/stdlib-2.7.0/libdoc/net/http/rdoc/Net/HTTP.html for info handling responses
• Both response.code and response.body must be checked
• Example response, when template coordinates are floats instead of integers (sprint does not allow floats for x and y):

code: 200
body: {"errors":[{"message":"Variable 'printRequest' has an invalid value: Expected type 'Int' but was 'Double'.","locations":[{"line":1,"column":16}],"extensions":{"classification":"ValidationError"}}]}

• Example response, template is broken and sprint cannot deserialize it.

code: 500
body: {"timestamp": "2023-08-02T14:46:30.160+00:00","status": 500,"error": "Internal Server Error","path": "/graphql"}

• If sprint cannot log in to printer, the details are available in response body.

• See https://github.com/sanger/sprint/blob/master/how_to_add_printers.md for info about security and configuration.

• A successful response has a 200 code and a job id in response body.