Fix test using a mock redirected response

[tintinthong]

This wud complete CS-5982

2 issues

• source fetching without an extension returns a 302, eg person. We usually rely on native fetch to follow this response, but since we use realm.maybeHandle in test our app just gets a 302
• source fetching with an extension doesn't return a response.url in host test, eg person.gts rather it returns response.url =''

Solution

create overriding url handlers that

• create a mock response that allows us to mutate return response.url. Response object doesn't allow this
• if we expect a redirect, just return the redirected response

There are ofcourse assumptions about how the handler overrides the request. I tried my best to restrict as much as possible and if the handler doesn't pick up the request just pass it along to its handlers set previously

[github-actions]

Test Results

388 tests  +373   381 ✔️ +370   5m 10s ⏱️ + 5m 0s
    1 suites ±    0       7 💤 +    4 
    1 files   ±    0       0 ❌  -     1 

Results for commit 927700f. ± Comparison against base commit cc90d68.

♻️ This comment has been updated with latest results.

[tintinthong]

If preferred for ease of review can merge this into the root branch -- feel free to do so (squash & merge wud b good)

[habdelra]

The approach looks good, but there a couple things you need to fix.

[habdelra]

testRealmPathURL is just the default test realm URL. There is an option to configure the test realm with a different URL and we do that for a few tests—don’t assume this is the realm URL.

[tintinthong]

hmmm ok fixed this. But I made the handler pass an argument (required) of realmURL. I thought ideally, I would build something higher order which allows the handlers to have realmURL,adapter and maybeHandle available but the change seemed a bit too much and made the handlers being passed more unclear. I prefer this way of forcing the test maker to specify the realmURL.