fix(NODE-6801): set token on connection from cache

[durran]

Description

When using OIDC authentication when there is more than one connection in the pool, connections that were created after the first connection would have no access token set on them until after the first reauthentication attempt. This was due to the fact that the first connection that was created retrieved the token and put it in the cache, and all following connections weren't setting their access token properly from the cache if it existed.

What is changing?

• Changes the machine workflow to properly set a token from the cache on the connection if the connection's token is undefined.
• Adds a unit test.

Is there new documentation needed for these changes?

None

What is the motivation for this change?

HELP-70195

Release Highlight

Fixed an issue in OIDC authentication where 391 reauthentication could fail.

This was due to a bug in setting the properly cached access token on the connection.

Double check the following

• Ran npm run check:lint script
• Self-review completed using the steps outlined here
• PR title follows the correct format: type(NODE-xxxx)[!]: description
  • Example: feat(NODE-1234)!: rewriting everything in coffeescript
• Changes are covered by tests
• New TODOs have a related JIRA ticket