Create Codespaces (CPU & GPU) Dockerfile's and devcontainer.json's

[mraarone]

Create dockerfile.devenv-codespaces-cpu and dockerfile.devenv-codespaces-gpu, then .devcontainer/devcontainer-codespaces-cpu.json and one for *-codespaces-gpu.json with the --gpus all flag.

[mraarone]

Remote and local devcontainers aren't compabile with Codespaces due to security issues with passing ssh-agent environment variables from host systems and the volume mount conduit for the SSH_AUTH_SOCK. GitHub didn't like it when I ran that devcontainer, something about I was trying to steal their keys. So... to create compability with the VSCode and Docker hosted VSC container created when a user clicks the GitHub Badge labeled "Remote Container - Open" on the repo's README.md page, for local docker container runs using the VSCode launched WSL - container using "code ." in WSL, and for the .devcontainer/devcontainer.json run on GitHub Codespaces... a forced compability is to hobble the default Codespace's launch via the green "Edit Code" button on the repo homepage for GitHub Codespaces. Instead, to run a GitHub Codespace using a devcontainer.json configuration, go to your account, your "Your Codespaces" page, and create a codepage using the folder in the repo of choice. This will allow CPU, GPU, scaled, etc. Codespaces to be defined for your development purposes, and it'll allow Remote and local VSCode devcontainers to retain almost exactly the same definition, using the same Docker Image in Docker Hub--keeping the purpose of dev containers, to keep them consistent.

I know that was long-winded, but that's about 2 weeks of research, trial, and error summed up into a paragraph.

[mraarone]

Oops, reopened.