This commit adds support for the Fetch API'smode andredirect options when usingHttpClient with thewithFetch provider.

The change includes:

• Addedmode andredirect to theHttpRequestInit interface
• ModifiedFetchBackend to pass the options
• Modifed in simple function in xhr to show warning messages
• Added unit tests to validate behavior

Motivation / Use Cases

Themode andredirect options are particularly useful for:

• mode controls the request's CORS policy ('cors', 'no-cors', 'same-origin'), helping manage security boundaries and cross-origin resource sharing.

• redirect determines how redirects are handled ('follow', 'manual', 'error'), allowing developers to explicitly accept, reject, or handle redirections manually.

• These options help ensure secure data access across origins, enforce strict network policies, and give developers more control over how external resources are handled.

Proposed Solution

• Addmode andredirect to theHttpRequestInit interface
• Implement property handling in theHttpRequest class
• Pass the options throughFetchBackend to the native Fetch API
• Maintain full backward compatibility

Examples of New Usage

// POST request with mode and redirecthttp.post('/api/register',{mode:'same-origin',redirect :'follow',}).subscribe();