fix: handle failed fetch error in multitenancy login methods

[ahielanravichandran]

Description

Fixes the handling of "Failed to fetch" errors when loading dynamic login methods.

Changes

• Removed error rethrowing in AuthPage and RoutingComponent
• Added proper error handling in FeatureWrapper
• Added error logging with proper TypeScript types

Testing plan

1. Start the app with the backend server down
2. Navigate to the login page
3. Verify that the error is properly handled and logged
4. Verify no infinite loops or unhandled promise rejections occur

Checklist for important updates

• Changelog has been updated
• frontendDriverInterfaceSupported.json file has been updated (if needed)
• Changes to the version if needed
  • In package.json
  • In package-lock.json
  • In lib/ts/version.ts
• Had run npm run build-pretty
• Had installed and ran the pre-commit hook
• Issue this PR against the latest non released version branch.
  • To know which one it is, run find the latest released tag (git tag) in the format vX.Y.Z, and then find the latest branch (git branch --all) whose X.Y is greater than the latest released tag.
  • If no such branch exists, then create one from the latest released branch.
• If added a new recipe interface, then make sure that the implementation of it uses NON arrow functions only (like someFunc: function () {..}).
• If I added a new recipe, I also added the recipe entry point into the size-limit section of package.json with the size limit set to the current size rounded up.
• If I added a new recipe, I also added the recipe entry point into the rollup.config.mjs
• If I added a new login method, I modified the list in lib/ts/types.ts
• If I added a factor id, I modified the list in lib/ts/recipe/multifactorauth/types.ts