Stub the entire instance method of IAMSSOeOAuth::Configuration in the IAMSSOeOAuth::SessionManager

[RachalCassity]

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Summary

Fixing the IAMSSOeOAuth::SessionManager flakey spec by stubbing the entire IAMSSOeOAuth::Configuration instance. The configuration used to be stubbed but was taken out, I believe on accident, when fixing a dependabot issue. The error can be found in this CI run .

Related issue(s)

• N/A

Testing done

• N/A - spec fix

Screenshots

Note: Optional

What areas of the site does it impact?

Improving CI specs

Acceptance criteria

• I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• No error nor warning in the console.
• Events are being sent to the appropriate logging solution
• Documentation has been updated (link to documentation)
• No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• Feature/bug has a monitor built into Datadog (if applicable)
• If app impacted requires authentication, did you login to a local build and verify all authenticated routes work as expected
• I added a screenshot of the developed feature

Requested Feedback

(OPTIONAL)What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?