Try to read .okta.yaml config file from working directory

[ConnorWidtfeldt]

Summary

The documentation makes it sound like the expected behavior regarding the .okta.yaml file is to read it from the applications directory. This, however, tries to read the config file from the shared library when not building statically. Instead of patching this behavior, in case somebody depends on it, I have added another check to try to load the config file from the applications working directory.

Fixes #349

Type of PR

• [X] Bug Fix (non-breaking fixes to existing functionality)
• [X] New Feature (non-breaking changes that add new functionality)
• [ ] Documentation update
• [ ] Test Updates
• [ ] Other (Please describe the type)

Signoff

• [X] I have submitted a CLA for this PR
• [X] Each commit message explains what the commit does
• [X] I have updated documentation to explain what my PR does
• [X] My code is covered by tests if required
• [X] I ran make fmt on my code
• [X] I did not edit any automatically generated files

[github-actions[bot]]

This PR has been marked stale because there has been no activity within the last 28 days. To keep this PR active, remove the stale label.

[github-actions[bot]]

This PR has been marked stale because there has been no activity within the last 28 days. To keep this PR active, remove the stale label.

[github-actions[bot]]

This PR has been marked stale because there has been no activity within the last 28 days. To keep this PR active, remove the stale label.