pin cryptography to avoid warning from parsl import

[LeiGlobus]

The latest globus-compute-endpoint, which upgraded to a more recent version of parsl, started generating this error message on endpoint CLI commands:

/opt/globus-compute-agent/venv-py39/lib/python3.9/site-packages/paramiko/pkey.py:100: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES a
nd will be removed from this module in 48.0.0.                                                                                                                                                               
  "cipher": algorithms.TripleDES,                                                                                                                                                                            
/opt/globus-compute-agent/venv-py39/lib/python3.9/site-packages/paramiko/transport.py:259: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.Triple
DES and will be removed from this module in 48.0.0.                                                                                                                                                          
  "class": algorithms.TripleDES,                                                                                                                                                                             
Created multi-user profile for endpoint named <some-endpoint-name>  

This was observed with 3.9, 3.12, and some environments of 3.10.

See slack thread with more context: https://funcx.slack.com/archives/C016JMYST9C/p1723232785192439

The temporary solution is to pin cryptography to a lower version until the parsl issue with PR parsl #3569 is deployed and Compute updates our parsl version to it.

Update
42.0.0 triggered a pip-audit security warning, so maybe better to wait for parsl to deploy the fix above and bump parsl version in Compute instead.

[khk-globus]

I'm not sure if the reference to the slack conversation is so relevant/interesting here. What might be better is to link to the related Parsl PR instead.

[rjmello]

Let's add this to the current release branch, v2.26.0, and bump the alpha version.

[LeiGlobus]

Parsl auto releases at 22:42 UTC (5:42 CT) on Monday. As I wrote on the thread, I'll wait for the release tonight, pin the new version, and see if the warning goes away. If it does, I'll redo this PR and add it to 2.26.0a1 (new alpha). If it doesn't, we can discuss further tomorrow.

[LeiGlobus]

Closing this PR in favor of #1623