Configure mypy in workspace

[DFriend01]

Description

• Relevant issue: Explore VS Code Python integration #39
• Install mypy in base container and create vscode task type check
• The mypy extension recently had an install release. It worked in the workspace with some success, but the linter sometimes wouldn't run automatically when a file opened like the documentation said. I commented out the vscode configuration for now and settled on creating a vscode task instead.
  • [Patrick] Seems to be working now, so enabled

To Do

• Add global launch and configuration files #154 is merged into main then main is merged into this branch
• mypy vscode task
• Generalize mypy vscode task (only one task)
• mypy CI passes
  • Figure out why CI errors different from when running ament_mypy src in the terminal
• Make mypy CI required
• Fix mypy extension errors If still getting errors with extension, remove from devcontainer.json

Once this is merged, create a new minor release

Verification

• Ran the vscode task and it works on multiple files (I have a lot of typing errors to fix later 😢)

[patrick-5546]

Converted to draft, see To Dos in PR description

[patrick-5546]

I think we have to run mypy in every directory that we want inside src rather than just at src like the other linters:

• Create a task to run for every python subdirectory of src
• Create meta task that runs all of these tasks
• Add meta task to lint task

[patrick-5546]

@DFriend01 for reference, here is how I resolved the errors in main_launch.py

• Fix mypy errors local_pathfinding#35

[patrick-5546]

Yay we did it