fix(meta-pixel): refine fbq type definitions

[tsukiyama-3]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ 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

This PR refactors the Meta Pixel (fbq) integration to improve type safety and developer experience.

• Adds explicit types for each valid fbq call pattern
• Adds support for additional Meta Pixel call patterns
  • trackSingle
  • trackSingleCustom
  • consent
• Adds a fallback [string, ...any[]] signature at the end to preserve compatibility with undocumented or custom usages
• Makes contents in EventObjectProperties optional to prevent type errors in common usage
• Updates documentation to reflect the new types

References

https://developers.facebook.com/docs/meta-pixel/advanced
https://developers.facebook.com/docs/meta-pixel/implementation/gdpr/

[vercel]

@tsukiyama-3 is attempting to deploy a commit to the Nuxt Team on Vercel.

A member of the Team first needs to authorize it.

[harlan-zw]

Awesome, thanks for your work on this, it's much better