Update composer dependencies

[dbudwin]

Description

Updating composer dependencies to the latest and greatest to help with security, testing, and maintainability.

Motivation and Context

Periodically updating composer dependencies is vital for the integrity and long-term success of this codebase.

How Has This Been Tested?

Andd current unit tests pass. The website also behaves as expected while testing locally.

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [X] Enhancement/Security (non-breaking change which is not noticeable to end users)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [X] I created a feature branch and did not open a pull request from my master branch.
• [X] My code follows the code style of this project.
• [ ] My change requires an update to the README and I have updated it accordingly.
• [X] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [X] This is a complete change and doesn't leave the project in a bad state.
• [X] All new and existing tests pass.