Fix deprecation warning from cryptography_backend.py

[ibrag8998]

More info in #221

[cbetta]

+1 to this, though I feel like this might break python-jose with older versions of cryptography. Depending on when this change was introduced to cryptography (and the python versions python-jose wants to support) it might be wiser to try the one method and then fall back onto the other?

[danielknell]

int_from_bytes is a python 2.x compatibility method, which is thankfully now EoL.

int.from_bytes/to_bytes were added in python 3.2 about a decade ago.

[danielknell]

it's probably worth updating the calls to int_to_bytes also which will cause the same warning.

[chitopunk]

see #207

[cbetta]

Ah excellent, I had not seen that PR. 👍🏻

[MasterSergius]

Is there any info on when this PR is going to be merged?

[blag]

I won't have time for at least another month.

I highly recommend that at least one person on this thread ask @mpdavis to also become a maintainer.

[alanyee]

I am willing to become a maintainer so that some of the trivial, stale PRs/issues can be solved. How do I sign up?

[blag]

@alanyee

ask @mpdavis to also become a maintainer.

[asherf]

#229 is now merged, I figured it would be faster than rebasing this PR so I cherry-picked the commit, PR'ed it and merged.
thanks for the fix!