DOCS-9362 Fix the CSRF page

[jescalan]

Important

🔎 Previews:

• https://clerk.com/docs/pr/1624/security/csrf-protection

Explanation:

The CSRF page contained inaccurate links and inaccurate statements, and generally didn't adequately explain what a CSRF attack is and how Clerk helps to prevent them. This set of edits should fix that up!

Also just food for thought - while Clerk does add a lot of important security guarantees throughout the product, this is one of the less impactful ones, since all we do is use the default value and not change the samesite flag on cookies to an insecure option. To be fair, there are plenty of cases in which people will do this and unwittingly open themselves to attack, but you'd kind of have to go out of your way to make a mistake in order to do so, which is why I say while it's not value-less, it's not our strongest security guarantee. Especially compared with the 1m expiration JWTs substantially hamper XSS attackers, which is a much more unique and impactful security feature of our architecture. And I don't think we really go through and explain that on any of our other docs pages, other than a VERY small mention here 🤷‍♂️

[github-actions]

Hey, here’s your docs preview: https://clerk.com/docs/pr/1624

[victoriaxyz]

Approved pending @alexisintech 👀