Add devcontainer.json for development with VS Code in a Docker container

[mkoeppe]

https://code.visualstudio.com/docs/remote/containers

We add two new sections in the developer's guide:
https://47f8b984ef964a5aa34147393fbdc32e0dde88ad--sagemath-tobias.netlify.app/developer/portability_testing.html#using-our-pre-built-docker-images-published-on-ghcr-io

We also set up devcontainer configurations for the CoCalc and computop/sage Docker images, as well as downstream distribution packaging of Sage.

• Cannot rebuild sage 3-manifolds/sagedocker#2

Tested devcontainer.json of

• portability-ubuntu-jammy-standard: builds well; runs well
• develop-docker-computop: builds well; runs well
• downstream-docker-cocalc: builds well; runs well (except machines with the issue Do not require AVX when building with SAGE_FAT_BINARY #32434)
• downstream-docker-computop: builds well; runs well
• downstream-archlinux-latest: builds well; runs well
• downstream-conda-forge-latest: builds well; runs well

Follow-ups:

• Installation guide: Document Sage installation on Windows via VS Code devcontainers #34363 Installation guide: Document installation on Windows via devcontainer
• Cookiecutter for Sage user projects with devcontainer #34286 Cookiecutter for Sage user projects with devcontainer
• .devcontainer/portability-ubuntu-jammy-standard fails in GitHub Codespaces #34403 GitHub Codespaces - may also be able to test it by starting a codespace at https:https://user-images.githubusercontent.com/5037600/216875765-6697bbf8-70f9-4acc-868e-9309db67be92.jpg/new?hide_repo_select=true&ref=public%2Fbuild%2Fdevcontainer&repo=302607352&machine=standardLinux32gb&devcontainer_path=.devcontainer%2Fdevcontainer.json
• downstream-* for more distributions (generate with tox from the info in tox.ini, use _sagemath` package)
• develop-conda-forge-src-environment-dev (https://doc.sagemath.org/html/en/installation/conda.html#using-conda-to-provide-all-dependencies-for-the-sage-library-experimental, similar to our gitpod configuration)
• Restore portability-debian-buster-i386-standard and fix it
• Restore develop-docker-cocalc (was: builds well (after increasing disk image space on the Docker daemon); fails to run)
• Restore - portability-centos-7-devtoolset-gcc_11-standard (was: builds well; fails to run (exactly the same on WSL))
• Restore downstream-docker-sagemath (after Update docker build #34242)
• add github workflows that verify that sage is at least compiling in these containers. That should be relatively straightforward using https://github.com/devcontainers/ci
• improve portability-Dockerfile as explained in comment:299

Depends on #33873
Depends on #34352

CC: @tobiasdiez @dimpase @williamstein @culler @saraedum @kwankyu

Component: user interface

Author: Tobias Diez, Matthias Koeppe, Kwankyu Lee

Branch/Commit: 4affef2

Reviewer: Kwankyu Lee, Matthias Koeppe

Issue created by migration from https://trac.sagemath.org/ticket/33671

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1 +1 @@
-
+https://code.visualstudio.com/docs/remote/containers

[mkoeppe]

Description changed:

--- 
+++ 
@@ -1 +1,4 @@
 https://code.visualstudio.com/docs/remote/containers
+
+see also https://github.com/gitpod-io/gitpod/issues/7721
+

[mkoeppe]

Dependencies: #29536

[tobiasdiez]

Author: Tobias Diez

[tobiasdiez]

Commit: 85a7100

[tobiasdiez]

Changed dependencies from #29536 to none

[tobiasdiez]

Branch: public/build/devcontainer

[tobiasdiez]

comment:5

A basic devcontainer definition is now added for ubuntu systems.

---

New commits:

85a7100

Add devcontainer for ubuntu