Description

This will greatly improve ergonomics for customers and our downstream libraries. Notably:

• GoogleAuth/AuthClient can be a drop-in replacement for libraries requiring fetch-API compliance

Here's an example for customers wanting this functionality:

• https://www.youtube.com/watch?v=IY-z00bfnOc&t=291s (from 4:51-5:10)

Impact

Customers can now streamline their request management to:

const auth = new GoogleAuth();
const fetchWithAuth: typeof fetch = (...args) => auth.fetch(...args);
await fetchWithAuth('https://example.com');

Testing

Added tests and updated some samples to use #fetch.

Additional Information

To avoid parsing/marshaling the returned data from GoogleAuth#fetch/AuthClient#fetch to GaxiosResponse#data, set {responseType: 'stream'} for the GaxiosOptions.
This can be useful when using this API as a drop-in replacement for fetch and the receiving API expects Response#bodyUsed to be false.
We could expose a noMarshalFetchData option here for AuthClientOptions or upstream in GaxiosOptions if this becomes a widely-desired feature.

Builds on:

• feat: fetch-Compatible API gaxios#680

🦕