Add a feature that installs dependencies from an Aptfile.dev file

[viktorianer]

Description:

This PR introduces a new feature for installing apt dependencies in the DevContainer environment using an Aptfile.dev file. The feature simplifies the process of managing apt packages required for the development environment by specifying them in a file and automating the installation during the container setup process.

Usage:

To use the feature, include the following in your devcontainer.json:

{
  "features": {
    "ghcr.io/devcontainers/features/apt:1": {
      "devFile": "../Aptfile.dev"
    }
  }
}

Example Aptfile.dev

# Video thumbnails
ffmpeg
libvips

# PDF thumbnails
poppler-utils

# PostgreSQL
libpq-dev
postgresql-client

Additional Information:

Based on the approach found in https://github.com/heroku/heroku-buildpack-apt and https://docs.digitalocean.com/products/app-platform/reference/buildpacks/aptfile/.

[viktorianer]

@microsoft-github-policy-service agree

[eitsupi]

@viktorianer Have you read the README and CONTRIBUTING.md?

This repository will accept improvement and bug fix contributions related to the current set of maintained Features.

features/CONTRIBUTING.md

Lines 20 to 28 in 302feca

	## Contributing code
	👨‍💼 This repository is a collection of dev container Features managed by dev
	container spec maintainers. This repository will **only accept improvements and
	bug fixes** for the [current set of maintained Features].
	🚀 If you're looking to create a new Feature, then we encourage adding it to a
	separate repository of your control. The [devcontainers/feature-starter]
	repository has more guidance on self authoring Features.

I don't think contributions to add new Features are acceptable.

[viktorianer]

Thank you for the feedback. I have reviewed those documents and understand that this repository focuses on improvements and bug fixes for the existing set of maintained Features.

I completely understand if adding a new Feature doesn’t align with the current goals of this repository.

If this contribution is not considered for merging, I’m happy to proceed by maintaining this Feature in a separate repository.

Thank you for your time and consideration!