CE-311 - logging everywhere

[eapearson]

CE-311 - logging everywhere

A couple weeks ago we added JSON logging in preparation for adding easily-analyzable logging generally and specifically for all ORCID API calls, as they recommend.

This is an effort to complete that logging.

Description

Add logging calls to all ORCID API calls.

Issues Resolved

• CE-311 - https://kbase-jira.atlassian.net/browse/CE-311

• Added the Jira Ticket id(s) to the title of the PR
• [ ] Added the Github Issue Ids to the title of the PR

Testing Instructions

One needs to have bash and docker installed.

git clone https://github.com/kbase/kbase-service-orcidlink
cd kbase-service-orcidlink
./Taskfile test

• Tests pass locally
• Tests and build pass in GitHub actions
• Manually verified that changes are available (if applicable)

Dev Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have run the code quality tools against the codebase

Release Notes - Development

This section only relevant to a PR against develop

• Ensure there is an "Unreleased" section located at the top of RELEASE_NOTES.md
• Add relevant notes to Unreleased

Release

This section only relevant if this PR is preparing a release

• [ ] Rename the "Unreleased" section to the appropriate release, and create a new, empty "Ureleased" section at the top