Feature Request: Accept alternative .hex runtime

Request that the Load/Save dialog accept custom .hex runtime (MicroPython interpreter runtime) that it uses for that project in-place of it's built-in runtime. This would be similar to functionality already in the Mu editor and would allow users to enjoy the same benefits.

This thought may be similar to subpostings in Issue #26

Suggestions:
- the runtime appears in the Project files list (file system list) of the Load/Save dialog.
- limit to 1 runtime per project (of course); new runtimes replace old runtime
- .hex file loading properly parses out user .py, modules, and runtime, if provided .hex is an entire project (rather than just a MicroPython runtime).

A issue não nomeia arquivos, testes nem pontos de entrada, então primeiro rastreie o diálogo Load/Save e o tratamento de arquivos de projeto no editor JavaScript. A conclusão deve incluir aceitar um runtime .hex do MicroPython específico do projeto, substituir um runtime existente e também tratar corretamente arquivos .hex que contêm arquivos de projeto.

Escrita pelo modelo de indexação a partir do texto da issue.