Replace CSRF token with Quarkus implementation

Since we initially implemented our CSRF token mechanism, the Quarkus implementation has matured and we have swapped base frameworks to the one required to bind to the Quarkus implementation: https://quarkus.io/guides/security-csrf-prevention

We should deprecate our current solution and switch to the Quarkus implemented one. The Quarkus CSRF tokens are stored in the auth session data and is encoded into an HTTPOnly cookie. This should be much more robust than our current solutions and also reduce the complexity of our stack overall.