Make Authentication middleware transition easier

[iMacTia]

Issue description

As discussed in #1358 (comment), it is currently not a straightforward process to support both Faraday v1 and v2 ways of adding authentication to a request.

CHECKLIST (delete before creating the issue)

• Make the authorization middleware work the same as v2 also in v1, while maintaining backwards compatibility
• Update documentation to explain what is possible in v1 and what will be available in v2

[ariana-paris]

While the documentation is being updated, can I put in a vote for an example of token authorization?

I understood the bit about changing my conn.authorization to conn.request :authorization, but then is it 'Token'? Is it :token? Do I still need the token: XYZ I have in my v1 code or is it just 'XYZ'? Is there a way to link to a complete list of the options rather than guessing based on the HTTP spec? I'd normally experiment but I'm still on v1.x so nothing works anyway, so just thought that would preempt the same questions when my future self has to use 2.x... Thanks! 😀

[iMacTia]

That's a fair point @ariana-paris, the documentation currently assumes a certain level of understanding of the code internals in order to achieve the desired result. This should also be addressed in scope of this ticket 👍. A few examples covering the most common HTTP Authentication mechanisms would be extremely useful.
Thanks for raising this!