Better error handling and logging for get operation status

[honourfish]

Overview

• Catch and handle http exceptions by logging them and carrying on the polling
• Introduce logging and log levels

Testing

Failure with log level WARNING:

python3 ./scitt/check_operation_status.py --operation-id foo
signed statement not registered within polling duration

Failure with log level DEBUG:

python3 ./scitt/check_operation_status.py --operation-id foo --log-level DEBUG
INFO:check operation status:starting to poll for operation status 'succeeded'
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): app.datatrails.ai:443
DEBUG:urllib3.connectionpool:https://app.datatrails.ai:443 "GET /archivist/v1/publicscitt/operations/foo HTTP/1.1" 400 47
DEBUG:check operation status:failed getting operation status, error: 400 Client Error: Bad Request for url: https://app.datatrails.ai/archivist/v1/publicscitt/operations/foo
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): app.datatrails.ai:443
DEBUG:urllib3.connectionpool:https://app.datatrails.ai:443 "GET /archivist/v1/publicscitt/operations/foo HTTP/1.1" 400 47
DEBUG:check operation status:failed getting operation status, error: 400 Client Error: Bad Request for url: https://app.datatrails.ai/archivist/v1/publicscitt/operations/foo
DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1): app.datatrails.ai:443
DEBUG:urllib3.connectionpool:https://app.datatrails.ai:443 "GET /archivist/v1/publicscitt/operations/foo HTTP/1.1" 400 47
DEBUG:check operation status:failed getting operation status, error: 400 Client Error: Bad Request for url: https://app.datatrails.ai/archivist/v1/publicscitt/operations/foo
...

[robinbryce]

I think we would do much better to hide the python specific traceback sytax

[robinbryce]

LGTM

[robinbryce]

LGTM