Modernise project codebase and update dependencies

[mreid-tt]

Summary
This update modernises the project configuration and dependencies to align with current specifications and framework updates.

Changes

• Updated project definition file to the latest specification
• Updated all project dependencies to their current stable versions
• Completed migration of the registration form to RegisterFormV2
• Refreshed .pre-commit-config.yaml with the latest versions of referenced repositories
• Used modern Flask-SQLAlchemy db.get_or_404() API instead of legacy Query.get_or_404()
• Bump project to Python 3.12 and removed unused dependencies

[mreid-tt]

Hey @publicarray, I've opened this PR to bring spkrepo and its build environment up to the latest specifications. I’d like to merge and deploy this as a stable baseline before introducing new functionality to the repository server.

Let me know if you’re available to help with review, testing, and deployment.

[mreid-tt]

Hey @publicarray, would now be a good time to consider moving to Python 3.12? I've gotten the build warnings down to three. All three warnings go away when we upgrade from Python 3.11 to 3.12. What are your thoughts here?

[mreid-tt]

Hey @publicarray, I've gone ahead and migrated the project to Python 3.12. I've also pruned some unused dependencies so we are neat and tidy. All tests report: 143 passed with no warnings.

[mreid-tt]

Hey @Diaoul, I don't know if you may have time to help review and deploy this PR. I'm preparing to work on #91 and #157 and would like to establish a clean baseline with this PR to build upon.

[Diaoul]

I'd say go ahead and merge! Better this than the status-quo. As for deploying, I have access to a new VPS, I can grant you root access there.

One idea I had was to deport the storage that is currently hardcoded to filepaths to a Minio instance deployed as part of the Docker deployment, I guess switching VPS would be a good opportunity for such a change.

[mreid-tt]

I'd say go ahead and merge! Better this than the status-quo. As for deploying, I have access to a new VPS, I can grant you root access there.

Ok, I can go ahead and merge but would have really liked it to be in production as well. For the new VPS, I know we discussed some initial migration strategies in #118. Did you confirm the new VPS has a CDN facility similar to the existing Fastly we use?

One idea I had was to deport the storage that is currently hardcoded to filepaths to a Minio instance deployed as part of the Docker deployment, I guess switching VPS would be a good opportunity for such a change.

I'm not deeply familiar with the existing VPS so I can only theorise what a migration could look like. I would need to have some discussions with @publicarray or yourself to better understand what is there now. However a fresh setup in the new VPS would be a useful way to test new features before cutting over.