Browser Redirect Support

[CalebGerman]

Initially built and tested this in a node enviroment for redirect. We did not support browser environments.

Redirect handling in Node vs browser

In Node (node-fetch), redirect: "manual" still exposes status and headers, so we can read Location and enforce our redirect policy. In browsers, the same setting yields opaqueredirect, which hides status/headers/body, so we can’t evaluate the redirect.

Using base fetch with default follow does not let us enforce our security measures before the redirect happens (Bentley-only domains, HTTPS-only, hop limits). In Node we can still do that with manual redirects; in browsers we can only validate the final URL after follow completes.

Solution

Now we have support for both while mataining more robust security in the node enviroment that we can not get with base fetch in browser enviroment.

Added playwrite tests to confrom browser enviroment is working.

#77

[wsm95]

lgtm