chore(encryptcookie)!: update default config

[sixcolors]

docs(encryptcookie): enhance documentation and examples

BREAKING CHANGE: removed the hardcoded "csrf_" from the Except.

Description

This PR introduces enhancements to the documentation of the Encrypt Cookie middleware. The changes aim to improve clarity, provide additional notes for users, and enhance code examples for better understanding and usage.

It also removes "csrf_" from the Except slice in the default config. Hardcoding exclusion values like "csrf_" in a middleware's default introduces inflexibility and interdependency among middleware components. The CSRF middleware can work with encrypted cookies, where front ends get plain text tokens from form input values or header mime tags, etc. And, this is generally considered a more secure configuration.

Details:

1. Documentation Updates:

   • Improve readability.
   • Used csrf.ConfigDefault.CookieName in CSRF example, instead of hardcoding "csrf_".
   • Highlighted the importance of middleware order.

2. Configuration Refactoring:

   • Removal of the hardcoded exclusion of "csrf_" from the Except slice in the default configuration (config.go).
   • Users can customize cookie exclusions based on their requirements.

3. Breaking Change:

   • The removal of the "csrf_" string from the default configuration is considered a breaking change.
   • Users relying on the previous default behavior may be impacted.

Fixes #2743

Type of change

Please delete options that are not relevant.

• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation - /docs/ directory for https://docs.gofiber.io/
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Commit formatting:

Use emojis on commit messages so it provides an easy way of identifying the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md

[gaby]

I'm not sure how we handle labels for this? The breaking change label will bump the major version from 2 to 3.

[sixcolors]

I'm not sure how we handle labels for this? The breaking change label will bump the major version from 2 to 3.

Since the core middleware are versioned with fiber I’m not sure either. The storage and contrib stuff we can version individually.

[ReneWerner87]

no problem we will mention it in the release, it is a breaking change but not a big one