CRAYSAT-1649: add error logging when unable to find token file path

[ethanholen-hpe]

Summary and Scope

add error logging when unable to find token file path and unwrap ~ as home directory

Issues and Related PRs

• Resolves CRAYSAT-1649
• Change will also be needed in <insert branch name here>
• Future work required by [issue id](issue link)
• Documentation changes required in [issue id](issue link)
• Merge after CRAYSAT-1649: Added ability for paths with a ~ to be unwrapped python-csm-api-client#48

Testing

List the environments in which these changes were tested.

Tested on:

• Rocket
• Drax
• Local development environment

Test description:

How were the changes tested and success verified? If schema changes were part of this change, how were those handled in your upgrade/downgrade testing?

• Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?
• Were continuous integration tests run? If not, why?
• Was upgrade tested? If not, why?
• Was downgrade tested? If not, why?
• Were new tests (or test issues/Jiras) created for this change?

Risks and Mitigations

Are there known issues with these changes? Any other special considerations?

Pull Request Checklist

• Version number(s) incremented, if applicable
• Copyrights updated
• License file intact
• Target branch correct
• CHANGELOG.md updated
• Testing is appropriate and complete, if applicable
• HPC Product Announcement prepared, if applicable

[ethanholen-hpe]

Output from Testing on Drax
https://gist.github.com/ethanholen-hpe/dfa1ad9b2575e5998ab7f0bd45dc5992

[ethanholen-hpe]

Testing on rocket: https://gist.github.com/ethanholen-hpe/f12537851c1c0b0cefb63d0142250195

[haasken-hpe]

Looks good. Minor comments.

[ethanholen-hpe]

/backport release/3.33

[github-actions]

Backporting into branch release/3.33 was successful. New PR: #297