Pyodide migration plan

[sra405]

Remaining tasks outstanding:

• Visualising sense_hat graphics using the modified sense_hat package
  • There is a work-in-progress pull request here
• Apply HTTP headers in a service worker (see Investigate setting Pyodide HTTP headers via a service worker #903)
  • Note that crossorigin will need to be added to cross-domain resources once the HTTP headers are added
• Add unit/integration tests that run real Python programs through the PyodideRunner.jsx
• Manual testing for backwards compatibility of existing Python programs, projects and the WebComponent
• Implementing the p5 package to work with Pyodide
  • See Support "python mode" for the p5 package and support the py5 package python-execution-prototypes#1
• Implementing a dedicated SQL editor for use in the Ada CS project
  • Note that Pyodide supports importing sqlite3 so we can add a UI wrapper around it

Originally posted in #893

Considerations:

• Is this an extensive list?
• Can we do a partial rollout? If so what would be needed when?
• Can we determine if the code in the editor requires Skulpt packages dynamically? (i.e. can we automatically utilise pyodide where appropriate and rollout indirectly?)
• Can we add pyodide to the web component?

Fixes required

• Input function asks for the answer before it tells you what the question is 😰
• Fix the chart.add function in pygal to accept a single value for the values argument as well as a list of values 📊
• Work out why the whls won’t load up on the staging site 🛞
• Stop the SenseHat resetting on every run 🔁
• Reduce latency between code runs by caching the modules interpreted from WebAssembly so this does not need to happen each time the code is run, possibly using a WebAssembly Module (see thread) ⏱️