ITVR - Resolve Dependency Update Issues for Frontend and Django

Description:

We have a number of dependency update issues that have been opened by the Dependabot. These updates need to be evaluated, tested and integrated into our development codebase. The identified dependencies are as follows:

word-wrap (frontend, javascript) needs to be bumped from 1.2.3 to 1.2.5 [#572]. This issue was opened 5 days ago and requires review.

certifi (django, python) needs to be bumped from 2022.12.7 to 2023.7.22 [#564]. This issue was opened last week and requires review.

cryptography (django, python) needs to be bumped from 36.0.2 to 41.0.2 [#558]. This issue was opened 3 weeks ago and requires review.

semver (frontend, javascript) needs to be bumped from 5.7.1 to 5.7.2 [#557]. This issue was opened 3 weeks ago and has been approved but not yet implemented.

django (django, python) needs to be bumped from 4.0.9 to 4.1.10 [#556]. This issue was opened last month and requires review.

Acceptance Criteria:

Each dependency update is reviewed for potential impacts on the existing codebase.
Any required changes to the codebase to accommodate these updates are implemented.
All unit and integration tests pass with the updated dependencies.
The application successfully builds and runs with the updated dependencies.
Changes are documented in the codebase as necessary.

Priority: High

This is high priority because keeping dependencies up to date is critical to the security, efficiency, and functionality of our application. Delays in these updates can lead to vulnerabilities and bugs, so it's crucial to integrate these changes as soon as possible.

Notes:

(1) Remember to follow the usual process for updating and testing dependencies: review the changelogs for the new versions, update the dependencies in a separate branch, run the tests, and manually verify the application functions as expected. If tests fail or manual testing uncovers issues, diagnose the problem, implement the necessary code changes, and repeat the testing process.

(2) The frontend Dependabot PRs update only package-lock.json, but I believe we npm install in all our environments; we don't clean install, which means we'll have to manually update package.json in order to actually use the updated packages.

(3) When updating the cryptography package, make sure that any encrypted fields that existed before the update can still be decrypted after the update.

(4) When updating certifi, make sure calls to external APIs (CHES, NCDA, Keycloak) all still work after the update.