feat(evlog): allow to configure request credentials in client logs & browser drain

[MrLightful]

📚 Description

Summary

• Add credentials option to BrowserDrainConfig (typed as RequestCredentials, defaults to 'same-origin')
• Allows 'include' for cross-origin ingest endpoints

Motivation

The browser drain & client log transport hardcode credentials: 'same-origin' in its fetch call. This works when the app and ingest endpoint share the same origin, but fails to send cookies/auth for cross-origin requests — a common scenario in local development (e.g., app on localhost:5173, API on localhost:3000) and production setups where the ingest endpoint lives on a separate domain or subdomain (e.g., app on app.company.com, API on api.company.com). Making this configurable unblocks these use cases without changing default behavior.

Usage

  createBrowserLogDrain({
    drain: { endpoint: 'http://localhost:3000/api/logs', credentials: 'include' },
  })

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.
• I have manually tested the feature in a use-case

[vercel]

@MrLightful is attempting to deploy a commit to the HRCD Projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

Thank you for following the naming conventions! 🙏

[pkg-pr-new]

npm i https://pkg.pr.new/evlog@232

npm i https://pkg.pr.new/@evlog/nuxthub@232

commit: 84926ce