Update to crypton >= 1.1.0 and ram instead of memory

[sumo]

The latest crypton (1.1.0) has now switched to ram instead of memory.

[georgefst]

Note that builds are currently failing due to the upper bound being too lax, and crypton-1.1.0 switching to ram:

[ 1 of 18] Compiling Crypto.JOSE.AESKW
src/Crypto/JOSE/AESKW.hs:53:11: error: [GHC-39999]
    • Could not deduce ‘ram-0.21.1:Data.ByteArray.Types.ByteArray
                          ScrubbedBytes’
        arising from a use of ‘ecbEncrypt’
      from the context: BlockCipher128 cipher
        bound by the type signature for:
                   aesKeyWrapStep :: forall cipher.
                                     BlockCipher128 cipher =>
                                     cipher -> Ptr Word64 -> (Int, Int) -> StateT Word64 IO ()
        at src/Crypto/JOSE/AESKW.hs:(42,1)-(47,24)
    • In the expression: ecbEncrypt cipher m
      In an equation for ‘b’: b = ecbEncrypt cipher m
      In a stmt of a 'do' block: let b = ecbEncrypt cipher m
   |
53 |   let b = ecbEncrypt cipher m
   |           ^^^^^^^^^^

This PR presumably fixes that, although another workaround otherwise for now is to add to a cabal.project:

constraints:
  crypton == 1.0.7,

Really, there should be Hackage revisions for all older versions of jose, specifying crypton < 1.1.

[shinzui]

This should be changed to >= 0.22