fix(azure_functions): preserve query string in adapter handler

[xMorthi]

🔗 Linked issue

• Resolves Azure Functions adapter does not forward query string to localCall #3588

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

The azure_functions preset discards query parameters when constructing the
URL passed to nitroApp.localCall. Currently it only uses:

const url = "/" + (req.params.url || "");

As a result, any query string is lost (getQuery(event) always returned {}).

This PR updates the handler to preserve the query portion from req.url
(if present):

let path = "/" + (req.params.url || "");
if (req.url && req.url.includes("?")) {
  path += req.url.slice(req.url.indexOf("?"));
}

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

@xMorthi is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[pi0]

Wondering why we are not using req.url in the first place instead of req.params.url? (/cc @danielroe if you remember any of the context)

[xMorthi]

To my understanding, its because req.url is full urlls https://domain... while req.params.url actually starts from api/

[pi0]

That's actually a good thing! We can use new URL(req.url) one step + also provide valid host header not sure if it is right or not currently.

[xMorthi]

I'm already running a few apps on Azure and haven't encountered any issues with accessing headers on the Nitro side. We pass the entire req.headers directly.