fix(oidc-client): harden error paths and fix wellknown e2e test assertion

The bad-wellknown e2e test was asserting on a message from the authorize.background()
code path, but the factory itself returns early with a "Failed to fetch well-known
configuration" error when the HTTP fetch fails — the background path is never reached.

Also moves pure helper functions out of authorize.request.utils into authorize.request
to reduce circular dependency risk, and simplifies buildAuthorizeOptions to a plain
function instead of a Micro effect.

Author: ryanbas21

e2e/oidc-suites/src/login.spec.ts

@@ -152,7 +152,7 @@ test('oidc client fails to initialize with bad wellknown', async ({ page }) => {
   await page.getByRole('button', { name: 'Login (Background)' }).click();
 
   await expect(page.locator('.error')).toContainText(
-    'Authorization endpoint not found in wellknown configuration',
+    'Failed to fetch well-known configuration from:',
   );
   await expect(page.locator('.error')).toContainText('wellknown_error');
 });