feat: ✨ add chromium via apt-get

[effendiian]

Chromium Installation via apt-get Package Manager

This pull request introduces one new feature for installing Chromium, for use as a headless browser, in devcontainers:

• Installs Chromium using the apt-get package manager and the release from the xtradeb/apps PPA repository.
• Leverages the apt-get-packages feature, which is already a part of the devcontainers-contrib/features index.

Example usage in a devcontainer configuration:

"features": {
	"ghcr.io/devcontainers-contrib/features/chromium-apt-get:1": {},
}

🔗 Resolves

This pull request affects the following issues:

• [Feature Request]: chromium-apt-get #626
• [Feature] Headless browser (chrome/chromium/firefox) devcontainers/features#189

📖 Context

There are some historical reasons for why it's being done this way:

• The official Chromium team doesn't supply "stable" binaries of Chromium; they are usually compiled into stable versions by third-parties.
• Chromium installation breaks when installed with snap packages on Ubuntu.
• apt-get install -y chromium on Ubuntu 20.04+ is just a wrapper for a snap installations.
• Referenced this guide to find a reliable PPA: How to Install Chromium Browser via PPA in Ubuntu 20.04, 20.10 - credit to UbuntuHandbook.

⚖️ Caveats

The maintainers may wish to scrutinize the default PPA used here, both for security and stability concerns. I agree!

I think future improvement to this feature could include:

• Parameterizing the selected PPA to allow sourcing chromium binaries from public and private PPAs.

🧪 Test Results

I ran tests locally, prior to creating this pull request and recevied these results:

┌ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┐
|    Dev Container Features   |   
│           v0.66.0           │
└ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ─ ┘

>  baseImage:         ubuntu:focal
>  Target Folder:     /workspaces/features
>  features:          chromium-apt-get

🏃 Starting test(s)...

🧪 Starting 'chromium-apt-get' tests...
🧪 Executing scenarios for feature 'chromium-apt-get'...
>  Running scenario:  test_ubuntu

📝 Scenario generated: {
  "image": "mcr.microsoft.com/devcontainers/base:ubuntu",
  "features": {
    "./chromium-apt-get": {}
  }
}
>  workspaceFolder:   /tmp/devcontainercli/container-features-test/1722128470487

⏳ Building test container...

# -- Omitted docker build output --

🚀 Launched container.
>  containerId:          8ddfc23fefc54823744a59a1ef074d15ad8b68506c54690247f497b55f6df366

🔄 Testing 'chromium --version'

Chromium 126.0.6478.182 built on Ubuntu , running on Ubuntu 22.04

✅  Passed 'chromium --version'!

Test Passed!
>  Running scenario:  test_debian

📝 Scenario generated: {
  "image": "mcr.microsoft.com/devcontainers/base:debian",
  "features": {
    "./chromium-apt-get": {}
  }
}
>  workspaceFolder:   /tmp/devcontainercli/container-features-test/1722128474781

⏳ Building test container...

# -- Omitted docker build output --

🚀 Launched container.
>  containerId:          bc1843d135f8013e9dccde04cc5d9d6cb7a9d4f6292e11a8c614e1e9e968663b

🔄 Testing 'chromium --version'

Chromium 126.0.6478.182 built on Debian 12.6, running on Debian 12.6

✅  Passed 'chromium --version'!

Test Passed!
🧪 Executing duplicate test for feature 'chromium-apt-get'...
⚠️ Skipping duplicate test for chromium-apt-get because '/workspaces/features/test/chromium-apt-get/duplicate.sh' does not exist.
🧹 Cleaning up 2 test containers...
🧹 Removing container bc1843d135f8...
🧹 Removing container 8ddfc23fefc5...

  ================== TEST REPORT ==================
✅ Passed:      'test_ubuntu'
✅ Passed:      'test_debian'

[evilhamsterman]

This project is not associated with the devcontainer project and appears to have been abandoned #628 . The official project has removed all devcontainer-contrib features from their listing. devcontainers/devcontainers.github.io#451. There is a fork that is being worked on to update and maintain the features https://github.com/devcontainers-extra/features

[effendiian]

Appreciate the heads up @evilhamsterman - Will look into moving this over to the new project.