[V3.1] Improved editor, Powered Up Remote, MicroPython modules

[laurensvalk]

Introduction
With so many people already using the Powered Up remote, it's easy to forget that this is just a beta. There have been numerous changes under the hood as well for improved performance and a better user experience.

Some of these changes aren't as visible from the outside, but they will pave the way for big upgrades coming in the near future.

We'd like to stabilize this and ship it before we work on big new features.

What's coming in V3.1

• New text editor within Pybricks Code.
  • Switch from Ace to Monaco for better editing experience.
  • Improved search and replace tools.
• Powered Up remote support
  • This was started as a popular end-user feature request: [Feature] Powered Up Remote Control #186
  • Still needs to be finalized: [Feature] Add "address" and "light" to class "remote" #404.
  • Lots of bluetooth performance upgrades for future stuff (yes!)
• Improved MicroPython experience
  • Enable additional features like slicing: [Feature] Enabling other MicroPython features #140.
  • Complete documentation of included MicroPython features, instead of referring to external documentation: Document included MicroPython modules pybricks-api#63
  • Compatibility overviews to make it easier to see what each hub supports. Add custom sphinx directive for compatibilty matrix pybricks-api#66
• Hub system attribute:
  • Disable or change stop button so you can use the center button in a script Using the buttons #233
  • Additional hub information [Feature] Hub name #52
  • Ability to shut the hub down from a user script.
• Ability to maintain motor position between scripts. [Feature] Make motor rotation sensor reset optional #389
• Stability improvements such as:
  • Improved shutdown behavior: https://github.com/pybricks/pybricks-micropython/issues/36
  • Firmware installation fixes like: [Bug] The hub took too long to respond (Android) #403

[dlech]

Release candidate is out at https://beta.pybricks.com.