State of Servant authentication

> I took over the maintenance after a lot of help from @alpmestan when I needed to figure out servant-auth. I share the same experience as others of wasting countless hours, but I did put a lot of those hours back so that it's a tiny bit better nowadays.

> Here's a short overview of incremental changes with the most impact:

> - write tutorials for common use cases (this would solve most of newcomers as they can have a working version they can revert to - see https://github.com/haskell-servant/servant-auth/issues/167)
> - remove XSRF being required for GET requests https://github.com/haskell-servant/servant-auth/issues/192
> - https://github.com/haskell-servant/servant-auth/issues/129

> Commonly requested features:

> - https://github.com/haskell-servant/servant-auth/issues/140
> - authorization https://github.com/haskell-servant/servant-auth/issues/119 https://github.com/haskell-servant/servant-auth/issues/73
> - not requiring JWT for cookie auth https://github.com/haskell-servant/servant-auth/issues/151

> Last but not least, the plan is to port servant-auth to servant and deprecate the old auth: https://github.com/haskell-servant/servant/issues/805

> These days I'm in brutal prioritization mode of scaling my business, so I can't do much maintenance but I do want to do everything I can for someone else to step up!

_Originally posted by @domenkozar in https://github.com/haskell-servant/servant-auth/issues/195#issuecomment-909959489_