fix(azure): correctly handle maxAge cookie option

[julien1619]

🔗 Linked issue

#2399

❓ 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

In the utils that sets cookies for Azure, it is lowercasing the cookie keys at line 24, so Max-Age becomes max-age:

const setCookieOptions = Object.fromEntries(
_setCookieOptions.map(([k, v]) => [k.toLowerCase(), v])
);

But uses another undefined key a few lines later:

maxAge: parseNumber(setCookieOptions.maxAge),

📝 Checklist

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

[pi0]

Thanks! (if you later find a way to add tests that would be awesome to avoid regression)