[Identity] Re-enable interactiveBrowserCredential test

[maorleger]

Per learnings below, figure out a way to correctly import MSAL 2.x in integration tests in identity

[maorleger]

Some learnings as I was digging into this:

MSAL 2.x and Azure SDK

Tests are failing with:

AuthError [NodeAuthError]: loopback_server_timeout: Timed out waiting for auth code listener to be registered.

Example build

Looking at MSAL's repo I found this issue by Matt, which was fixed in 2.x

Trying to upgrade to MSAL 2.x causes a different error when running integration tests:

Error: Cannot find module '@azure/msal-node'

This also prevents us from upgrading communication-identity's MSAL version to 2.x

So what's going on here (at least as far as I can tell)?

• communication-identity depends on 1.x
• identity depends on 2.x
• 2.x is ESM first with exports field controlling whether CJS or ESM is called: package.json
• our dependency, esm ignores exports field and was never updated to understand it: bug report
• when identity tests run, they try to find msal-node, but the only CJS they can find is 1.x
• Removing 1.x from our monorepo forces it to try and find 2.x, but is unable to because the esm package does not support it
• only integration-tests are failing, as the regular tests use ts-node and typescript sources directly. I dont know why we use esm in one and not the other, so I will need to ask around!

What can we do?

• Wait for Matt's work on ESM, or support his work to unblock
• Find a workaround to the esm package in the meanwhile
• Ask MSAL to bring back the main field in package.json
• Switch to an ESM fork in the meanwhile: https://www.npmjs.com/package/@httptoolkit/esm as an example
• Use vitest, which may allow us to avoid depending on the esm package entirely

Just to make things much easier to understand I isolated the incompatibility between MSAL 2.x and the esm package - you can see that in this minimal repro

Might be I am missing something super obvious!

[maorleger]

Linking to previous PRs:
#28346
#28374