Adopted sha256 for CSRF token generation and improved CSRFError handler + tests

[BarcoMasile]

Description

This PR takes care of three things:

• switches to sha256 for the strategy used when creating a CSRF token
• in case of a CSRF token error the cookie gets deleted
• tests are adjusted and added for csrf exception handler

How Has This Been Tested?

• unit tests
• e2e
• manual tests running "state changing" requests that trigger the csrf token check

PR Quality Checklist

• [x] I added tests to new or existing code
• [ ] I removed hardcoded strings and used our i18n solution instead (see here)
• [x] I made sure no sensitive info gets logged at any time in the codebase (see here) (e.g. no user info or details, no stacktraces, etc.)
• [ ] I checked that infrastructure/update_infrastructure.sh runs without any error
• [x] I checked that npm run build builds without any error
• [x] I checked that clusters are listed correctly
• [x] I checked that a new cluster can be created (config is produced and dry run passes)
• [x] I checked that login and logout work as expected

In order to increase the likelihood of your contribution being accepted, please make sure you have read both the Contributing Guidelines and the Project Guidelines

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.