feat: infer package manager from container exec and set package as an interface

[musdotdigital]

We strip reliance on parsing dockerfile to determine the package manager, we now execute the container in order to determine the package manager to use. This mean that we can support a wider range of dockerfiles without needing custom logic added.

A quick change to use package as an interface as opposed to a class is cleaner in implementation and provided a nice downstream feature to the updater. We can now parse multiple keys from the dependency, while continuing to only be concerned with name and version. As dependency manifests containing extra keys are not overwritten by the updater, we can now support declarations such as this:

[
  {
    "name": "git",
    "version": "2.34.1-r0",
    "extraKey": "field"
  }
]

In this PR we also provide support for ubuntu flavoured images such as the nvidia/cuda.

How to test

npm run build && npm run test

You can test this with different images by providing a new dockerfile and dependency to main.test.ts, for example I tested this for the an nvidia image with

FROM nvidia/cuda:11.8.0-runtime-ubuntu22.04

and updating dependencies.json to:

[
   {
        "name": "nvidia-docker2",
        "version": "2.13.0-1",
        "reason": "docker"
    }
]

[mblottiere]

This probably deserves a v1.1.0