feat(docs): add security to docs

[vejja]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

This allows to deploy docs with Nuxt Security enabled.
This is a first step towards obtaining a security score that can be displayed on the site: see #446

Description

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
nuxt-security	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 12, 2024 2:30pm

[vejja]

Docs now deployed with security headers

• securityheaders.com score: A+

• mozilla observatory score: A+

[Baroshem]

Great piece of work Sebastien! I am glad thatwe will have this as a part of our docs!

You cans afely merge right now to the RC branch :)

[vejja]

Great piece of work Sebastien! I am glad thatwe will have this as a part of our docs!

You cans afely merge right now to the RC branch :)

Will do now
Can you change the Vercel deploy settings to disable the Live Comments ?
Reason is: this feature injects a post-build script which is not SRI-protected. Removing the script will improve our Mozilla score