feat: Use mise to manage dev tools

[disaac]

• Updated DEVELOPMENT.md to reflect actual tool versions that were specified in Dockerfile and packages.json
• Added mise.toml and included the pinned tool versions setting uv and docker-compose to latest.
• Using uv to manage python version and virtual environment to ease and simplify setup.
• Created tasks in mise.toml to execute previously outlined steps in the DEVELOPMENT.md.
• Updated DEVELOPMENT.md to use mise task commands to execute development tasks. Also reorganized the DEVELOPMENT.md file so that the tasks can be executed in the order they are presented. Previously the dependencies were mentioned at the end which would cause celery to fail since the redis service wasn't running.
• Created a docker-compose.dev.yml that will expose the ports avoiding the need to uncomment this in the main docker-compose.yml file and added it as an override file in the mise task commands to ease development workflow.
• Updated cryptography in requirements.txt to higher version so that it will avoid trying to build on latest macos installations and just installs the wheel.
• Added a ty.toml in case its being used by the developer. This is a common formatter/linter used in the Zed editor. The ty.toml allows the nefarious imports to properly be handled when opening the project in the editor at the project root.

Closes Github Issue: #395

[lardbit]

nefarious is unfortunately still on django 3. I started an upgrade recently but got hung up on some end to end testing.

Can you update this PR to reflect django 3 and verify it still works ok? I'll test it out afterwards. I've never seen mise.

[lardbit]

doh - I misread the django version. My mistake. Let me test this out with mise.