Improve development speed by linting for circuit python spec

[nateinaction]

Recently tried running #26 on the satellite and received the following error no module named 'dataclasses'. We should try to lint to ensure all code adhears to the micropython circuit python standard so devs receive quick feedback to know that their code will work at least run when uploaded to the satellite. I suspect this would have saved me about an hour.

[nateinaction]

Research notes:
Started off with a blog article describing a vscode micropython linting setup which lead me to micropy-cli. micropy-cli aims to offer linting, intellisence, autocompletion, and dependency management for free as long as you can specify the board you're using. I then started trying to understand how to specify our custom board definition and with Michael's help was pointed to the CircuitPython build data for the Proveskit board. Finally I found the CircuitPython Stubs package and a pretty recent issue describing an imperfect but serviceable way to set up a custom stub pinout.

[nateinaction]

Ultimately what I have found is that you can install circuit python stubs with the circuitpython_setboard command. However your board needs to be included in a circuitpython release. The circuitypython team has a guide on how to add your board here.

It looks like we also must have a unique VID:PID for the board: https://learn.adafruit.com/how-to-add-a-new-board-to-circuitpython/frequently-asked-questions

[nateinaction]

Contributing the v4 board definition to the circuitpython repo is in-flight but waiting on our USB VID:PID application.

• Application: Add Bronco Space org and proveskit-rp2040-v4 pid pidcodes/pidcodes.github.com#1007
• Board definition introduction branch: https://github.com/adafruit/circuitpython/compare/main...proveskit:circuitpython:proveskit-rp2040-v4?expand=1