adjust backend to handle new mysql server, adjust front-end functiona…

[FancMa01]

…lity slightly

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Vulnerability fix (package bumps or CodeQL adjustments to ensure code security)
• This change requires a documentation update

Developer Checklist:

• I have commented my code, particularly in hard-to-understand areas
• I have resolved any conflicts with the branch I am attempting to merge to.
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings
• I have ensured that my code does not unecessarily duplicate existing cod
• I have ensured that all security checks have been passed
• All input boxes have sensible character limits applied
• Refreshing related pages puts page in a workable and sensible state

Reviewer Checklist

• I have pulled the branch into my local environemtn and started the project succesfully
• I have reviewed the code for proper comments and mispellings
• All input boxes have sensible character limits applied
• Refreshing related pages puts page in a workable and sensible state
• Submitting any relevant Forms relays proper messaging to user
• I have checked that all security checks have been passed
• I have checked that all backend routes have proper validation

[ydahal1]

Overall, the changes look good! One minor suggestion: Since we're no longer using the MSSQL package, let's go ahead and remove it from the codebase. Once that's done, this PR should be good to merge