fix(azure-identity,msal-node): fix double-registration in mock README example

The Testing section called enableAuthMock(configurator) once for its
return value, then again with a configure callback to seed the account.
The second call replaces the first provider (enableAuthMock always
registers last), so the retained `auth` reference from the first call
was no longer the active provider by the time login/acquireAccessToken
ran against it.

Collapse to a single enableAuthMock call that both seeds the account
and returns the provider that stays registered.

Addresses review feedback on PR #5244 (copilot-pull-request-reviewer).

Author: odinr

packages/modules/azure-identity/README.md

@@ -123,11 +123,8 @@ that need to exercise sign-in, sign-out, or token-refresh/expiry logic, use
 ```typescript
 import { enableAuthMock } from '@equinor/fusion-framework-module-azure-identity/mock';
 
-// default identity, already signed in
-const auth = enableAuthMock(configurator);
-
-// or seed the identity/state up front
-enableAuthMock(configurator, (auth) => {
+// seed the identity/state up front; omit the callback for a default, already-signed-in identity
+const auth = enableAuthMock(configurator, (auth) => {
   auth.setAccount({ username: 'ada@equinor.com', signedOut: true });
 });
 

packages/modules/msal-node/README.md

@@ -106,11 +106,8 @@ that need to exercise sign-in, sign-out, or token-refresh/expiry logic, use
 ```typescript
 import { enableAuthMock } from '@equinor/fusion-framework-module-msal-node/mock';
 
-// default identity, already signed in
-const auth = enableAuthMock(configurator);
-
-// or seed the identity/state up front
-enableAuthMock(configurator, (auth) => {
+// seed the identity/state up front; omit the callback for a default, already-signed-in identity
+const auth = enableAuthMock(configurator, (auth) => {
   auth.setAccount({ username: 'ada@equinor.com', signedOut: true });
 });