…MONGOSH-2147 (#211)

* fix: use ID token expiry if `passIdTokenAsAccessToken` is set MONGOSH-2145

* fix: do not return token to driver which is being rejected MONGOSH-2147

Ensure that we do not return tokens from a token set that the driver
is currently rejecting (in the sense of calling the OIDC callback
again and referring to it via the driver `refreshToken` property).

Co-authored-by: addaleax <899444+addaleax@users.noreply.github.com>

…215)

Co-authored-by: addaleax <899444+addaleax@users.noreply.github.com>

Co-authored-by: Anna Henningsen <anna.henningsen@mongodb.com>

It came up in conversations that OIDC connections in Compass fail frequently,
but we do not have real insight into why that is and what the most common
errors are overall.

Co-authored-by: addaleax <899444+addaleax@users.noreply.github.com>

Co-authored-by: addaleax <899444+addaleax@users.noreply.github.com>

These seem to have started to fail recently too, without changes to the
code itself (i.e. possibly only because of infrastructure or external
dependency changes such as Chrome updates).

…stance MONGOSH-2444 (#228)

`node-fetch` currently does not return a body that is a web/standard
`ReadableStream`, which is what openid-client expects. Since it only
makes use of this in error cases, no additional cases are broken,
but the error message is highly unhelpful in these cases.

Unfortunately, it is not trivial to resolve this without fully wrapping
the `node-fetch`, so this provides a limited compatibility layer rather
than a full-featured one.

Co-authored-by: addaleax <899444+addaleax@users.noreply.github.com>

… (#230)

* fix: improve error message for generic openid-client error MONGOSH-2487

Similar to previous commits, this change ensures that diagnostic information
is not lost through recent changes to openid-client's error system, where
currently a number of errors are grouped together under "something went wrong"
(https://github.com/panva/openid-client/blob/a1e4a4fd88fcdff12d88e3ff73f3e27fe5df4252/src/index.ts#L975)
and the library expects consumers to consistently expose the `cause` property
of the error object.

This also unifies the two existing `messageFromError` and `errorString`
implementations, which happened to duplicate each other.

* fixup: electron compat

* fixup: do not add "[object Response]" to errors

* fixup: add anchors to regex

Co-authored-by: addaleax <899444+addaleax@users.noreply.github.com>