[SCHEMATIC-245] fix security risks in packages

[linglp]

Fixed the following security risks:

• updated flask version to "2.2.5" to fix: https://github.com/Sage-Bionetworks/schematic/security/code-scanning/22
• updated flask-cors version to Flask-Cors = "^4.0.2" to fix: https://github.com/Sage-Bionetworks/schematic/security/code-scanning/29
• updated setuptools to setuptools = "^70.0.0" to fix: https://github.com/Sage-Bionetworks/schematic/security/code-scanning/25
• Updated cryptography to >=42.0.4" to fix: https://github.com/Sage-Bionetworks/schematic/security/code-scanning/20 and https://github.com/Sage-Bionetworks/schematic/security/code-scanning/19
• Since pyopenssl depends on cryptography, I also had to update pyopenssl to "^24.0.0"

Note:
Can't fully resolve issue related to werkzeug because of a breaking change in connexion 3.0.0 and above: See issue: SCHEMATIC 244

[BryanFauble]

Let's make sure the tests all pass, and run some manual regression testing when this gets deployed to AWS. Otherwise, the changes make sense!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud