feat: Add logRequestDetails option to withAxiomRouteHandler

[gabrielelpidio]

This PR introduces an optional configuration object that contains a logRequestDetails property to specify if and whether to include detailed request information.

Example of usage

export const GET = withAxiomRouteHandler(
  async () => {
    return new Response("Hello World!");
  },
  { logRequestDetails: true }
);

or

export const GET = withAxiomRouteHandler(
  async () => {
    return new Response("Hello World!");
  },
  { logRequestDetails: ['body', 'nextUrl'] }
);

[vercel]

@gabrielelpidio is attempting to deploy a commit to the AxiomFM Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

Deployment failed with the following error:

The provided GitHub repository does not contain the requested branch or commit reference. Please ensure the repository is not empty.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
next-axiom-example	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 21, 2024 5:25pm

[c-ehrlich]

Code looks good. Some small docs suggestions included.

Significant topic: I am not sure details is the best name for this api. Won't block on that, but maybe ask someone else for their opinion on this. I would suggest something along the lines of include(Req|Request), log(Req|Request) but not 100% on those suggestions either.