Educates refactoring

[jorgemoralespou]

Refactoring to avoid code duplication.

• We have added examples to every command, added arguments validation and refactored/moved code around.
• Upgraded functionality for educates local config edit that does validation and prevents saving on error
• New educates local mirror list command
• Docker compose has been upgraded from v2 to v5.0.1 to later support more local capabilities. Fixes Support docker compose v5 #817
• Updates kind to latest (0.31.0)
• Adds a --kubernetes-version flag to educates create-cluster and defaults to 1.34 and defines the kind images by sha to use.
• Refactored registry and mirror code to remove code duplication and improve performance
• Enhancements to educates docker workshop deploy. It creates port bindings for additional services containers.
• Adds labels to all educates containers in docker.
• Added multinode support for local educates (1 control plane, up to 5 worker nodes) (Added docs)
• Added support for node labels and node taints. Specially useful on multinode. (Added docs)

This has been rebased on latest develop, and updated to supersede #855. More commits will come later but guaranteeing that we keep this aligned with develop.

• Local registry will now get by default 172.18.200.1 (so kind network with 200.1 as offset) Fixes Local kind cluster ip change might cause issues #850
• Every mirror will also get a similar offset but hashed by registry name and if there's collision, will increase by 1 until available. Fixes Local kind cluster ip change might cause issues #850
• We have simplified how the check for port 80/443 availability on cluster creation was done
• We now detect if it's a disconnected install (by checking connection to docker hub) and if not available, we set do skip-image-resolution at install time.

With these changes, you can now survive Docker Desktop restarts and also install Educates on a machine without internet connection (as long as prepopulated mirrors and docker images are already present on the system). Supersedes #851

[GrahamDumpleton]

You managed to revert version to an older one, overriding recent updates due to CVE and npm audit. Possibly reverted package-lock.json files as well in other places, so npm audit will need to be done again.