Dev container changes for easier ROM uploading from the docker container to the SC64

[Polprzewodnikowy]

Description

I've made some changes to deployment and build process to simplify loading built ROM from the inside of docker container.
This method involves running sc64deployer tool (https://github.com/Polprzewodnikowy/SummerCart64/releases/tag/v2.14.0) on host machine in server mode. Docker container uses the same tool but it connects to the server via TCP connection.

To use this deployment method:

1. Run tool in server mode on host machine: sc64deployer server
2. Run deployment script in docker machine: ./sc64deploy.sh (add -d argument to automatically start debug mode)

Libdragon submodule has been switched to unstable branch.

Dockerfile now uses standard Ubuntu image instead of dedicated N64 toolchain image.

Devcontainer config has been updated to build libdragon submodule after creating container.

GitHub actions can be updated to use devcontainer dockerfile.

Motivation and Context

Described above.

How Has This Been Tested?

On local environment with Windows OS host and SC64.

Screenshots

Types of changes

• Improvement (non-breaking change that adds a new feature)
• Bug fix (fixes an issue)
• Breaking change (breaking change)
• Config and build (change in the configuration and build system, has no impact on code or features)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

Signed-off-by: Polprzewodnikowy [email protected]

[networkfusion]

Has the license changed?

[networkfusion]

Although, I guess we are not actually using anything from it, so it falls into fair use.

[networkfusion]

surely should be used instead of (or call) sc64deploy.sh

[networkfusion]

Not sure if this commented out code should be removed as the aim would be to add unit tests where possible (given it is a placeholder before merge into the main repo)...

[networkfusion]

Can this be updated rather than removed? or does a deploy now work well on a windows dev container?

[networkfusion]

It turns out that it is quite difficult to work between a branch that is a fork on a branch... but I have "fixed" the minify bits.
My main feeling at this point is the original libdragon docker should be improved (I already have a PR against it (see @rasky fork... , but will continue to integrate.

[networkfusion]

It seems that using git submodule update breaks this.

[networkfusion]

Completion of this PR is currently being carried out in https://github.com/networkfusion/N64FlashcartMenu/tree/test-libdragon-unstable . I have run into a few annoying things, like needing the sc64deployer not being compatible with debian slim (or probably other older linux versions for that matter), but nearly there.

[networkfusion]

Closing as superseeded.