feat: Remove docker_py usage in favor of custom client that uses Docker CLI (#33)

#### Relevant issue or PR
Fixes #10 
Enables #8

#### Description of changes
- Created a new `docker_client.py` file that contains a
`CLIDockerClient` class that is a custom python wrapper over
`docker_cli` that mimics the interface of `docker_py`.
- The file has 3 additional classes, `Container`, `Compose`, and
`Image`.
- Removed a lot of functions from existing files (all calls to
subprocess) and docker errors. Migrated them to the `docker_client.py`
and replaced errors with our new errors.
- `teardown` function in cli has the most amount of changes as handling
of `--all` flag is moved to `engine.teardown` instead as we no longer
need to filter through all the projects in docker and parse which ones
belong to Tesseract as our `DockerWrapper` class already knows all the
projects that are Tesseracts.
- Renamed `_display_container_meta` to `_display_project_meta` as I
think it's more fitting to the function since we are listing the
metadata of all the containers in a project, aka the project's metadata.
- Modified some unit tests to fit the new mocked class.

BREAKING CHANGE: Tesseract Core does not clear build caches anymore.
That means, the option `--keep-build-cache` and environment variable
`TESSERACT_KEEP_BUILD_CACHE` are now removed, and users are advised to
clean up Docker resources manually as needed (e.g. via `docker system
prune`).

#### Testing done
Unit tests + Manually tested commands:
`serve` `build` `ps` `list` `teardown` `teardown --all` `apidoc`

#### License

- [x] By submitting this pull request, I confirm that my contribution is
made under the terms of the [Apache 2.0
license](https://pasteurlabs.github.io/tesseract/LICENSE).
- [x] I sign the Developer Certificate of Origin below by adding my name
and email address to the `Signed-off-by` line.

<details>
<summary><b>Developer Certificate of Origin</b></summary>

```text
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
```

</details>

Signed-off-by: [Angela Ko] <angela.ko@simulation.science>

---------

Co-authored-by: Dion Häfner <dion.haefner@simulation.science>

Author: angela-ko

docs/content/creating-tesseracts/advanced.md

@@ -82,13 +82,6 @@ various circumstances:
  only be printed if something fails; this means that your shell might appear unresponsive
  during this process. If you want more detailed information on what's going on during your
  build, and see updates about it in real-time, use `--loglevel debug`.
-- By default `tesseract build` does not cache the various steps of building a Tesseract[^1].  This is a good choice once your Tesseract is mature enough (i.e., once you are not re-building frequently). While you are still implementing new features in the Tesseract and rebuilding it
- often, we recommend to use `--keep-build-cache` flag to keep your build steps in the cache,
- so that the next `tesseract build` runs faster.
- ```{note}
- A single `tesseract build` command without
- the `--keep-build-cache` option will invalidate the cache.
- ```
 - `--config-override` can be used to manually override options specified in the `tesseract_config.yaml`,
  for example: `--config-override build_config.target_platform=linux/arm64`
 - `tesseract build` relies on a `docker build` command to create the Tesseract image. By
@@ -100,11 +93,11 @@ various circumstances:
 
 ## Building Tesseracts with private dependencies
 
-- In case you have some dependencies in `tesseract_requirements.txt` for which you need to
- ssh into a server (e.g., private repositories which you specify via "git+ssh://..."),
- you can make your ssh agent available to `tesseract build` with the option
- `--forward-ssh-agent`. Alternatively you can use `pip download` to download a dependency
- to the machine that builds the Tesseract.
+In case you have some dependencies in `tesseract_requirements.txt` for which you need to
+ssh into a server (e.g., private repositories which you specify via "git+ssh://..."),
+you can make your ssh agent available to `tesseract build` with the option
+`--forward-ssh-agent`. Alternatively you can use `pip download` to download a dependency
+to the machine that builds the Tesseract.
 
 ## Customizing the build process
 
@@ -140,10 +133,9 @@ For example:
 ## Tesseracts without containerization
 
 While developing a Tesseract, the process of building and rebuilding the
-tesseract image for quick local tests can be very time-consuming. Using
-`--keep-build-cache` ameliorates this issue, but the fastest and most
-convenient way to speed this up is to just run the code you are developing
-in your virtual environment.
+tesseract image for quick local tests can be very time-consuming. The fastest and most
+convenient way to speed this up is to just run the code you are developing directly
+in your virtual Python environment.
 
 In order to do so, you should:
   - Make sure you have a development installation of Tesseract (see <project:#installation-dev>).
@@ -181,9 +173,3 @@ Python package. In order to do so, you can run `tesseract init` in the root fold
 your package (i.e., where `setup.py` and `requirements.txt` would be). Import your package
 as needed in `tesseract_api.py`, and specify the dependencies you need at runtime in
 `tesseract_requirements.py`.
-
-[^1]: There are several reasons for this. We wanted to make Tesseracts friendly to
-people unfamiliar with Docker, and this default reduces the chance of them accidentally filling their
-hard drives with data. Also, in a typical SciML setting, cache gets
-invalidated quite fast, so a lot of the data which would be saved to the disk
-would not really help with build times.

inject_runtime_pyproject.py

@@ -24,6 +24,7 @@
         "tesseract-core[runtime]",
     ],
     "dev": [
+        "docker",
         "fastapi",
         "httpx",  # required by fastapi test client
         "jsf",

production.uv.lock

@@ -8,7 +8,6 @@ authors = [
 license = { text = "Apache-2.0" }
 requires-python = ">=3.10"
 dependencies = [
-    "docker",
     "jinja2",
     "rich",
     "typer",

pyproject.toml

@@ -10,8 +10,6 @@ click==8.1.8
     # via typer
 colorama==0.4.6 ; sys_platform == 'win32'
     # via click
-docker==7.1.0
-    # via tesseract-core
 idna==3.10
     # via requests
 jinja2==3.1.6
@@ -32,14 +30,10 @@ pydantic-core==2.33.0
     # via pydantic
 pygments==2.19.1
     # via rich
-pywin32==310 ; sys_platform == 'win32'
-    # via docker
 pyyaml==6.0.2
     # via tesseract-core
 requests==2.32.3
-    # via
-    #   docker
-    #   tesseract-core
+    # via tesseract-core
 rich==14.0.0
     # via
     #   tesseract-core
@@ -58,6 +52,4 @@ typing-extensions==4.13.2
 typing-inspection==0.4.0
     # via pydantic
 urllib3==2.4.0
-    # via
-    #   docker
-    #   requests
+    # via requests