Alias docker images internally

Some of the images used by Starforge are simply extra tags on other images:
- `starforge/purepy-wheel:latest` :arrow_right: `starforge/debian-wheel:6`
- `starforge/base-wheel:latest` :arrow_right: `starforge/debian-wheel:6`
- `starforge/base32-wheel:latest` :arrow_right: `starforge/debian32-wheel:6`

This results in the "aliases" appearing as separate images [in Docker Hub](https://hub.docker.com/r/starforge/), which is annoying/confusing. In addition, each "image" requires a separate push (which doesn't make sense to me, if they have all the same underlying layers and the same image ID shouldn't pushing aliases of already-pushed images result in "Image already exists" messages for each layer? Unfortunately that's not the case:

``` console
nate@weyerbacher% docker push starforge/debian-wheel:6
The push refers to a repository [starforge/debian-wheel] (len: 1)
8a40c04093cd: Image already exists
ee2d5171de71: Image successfully pushed
2e3c8128fa02: Image successfully pushed
5b7a9e06dfda: Image successfully pushed
991a3085cc57: Image successfully pushed
d0e6975c75d2: Image successfully pushed
60eb7aaceb8a: Image successfully pushed
11f17e6c581c: Image successfully pushed
134ff8959711: Image successfully pushed
134ff8959711: Buffering to Disk
b7336fb73419: Image already exists
9e94b6f5e953: Image already exists
d834be925c79: Image already exists
4c115374adfc: Image successfully pushed
Digest: sha256:a406dcc8d6b33cecfbe6bad12123527ec10dae61067782709419c45525d0cfe6
nate@weyerbacher% docker push starforge/purepy-wheel:latest ~/git/starforge/wheels/image
The push refers to a repository [starforge/purepy-wheel] (len: 1)
8a40c04093cd: Image already exists
ee2d5171de71: Image successfully pushed
ee2d5171de71: Buffering to Disk
5b7a9e06dfda: Image successfully pushed
991a3085cc57: Image successfully pushed
d0e6975c75d2: Image successfully pushed
d0e6975c75d2: Buffering to Disk
11f17e6c581c: Image successfully pushed
134ff8959711: Image successfully pushed
134ff8959711: Buffering to Disk
b7336fb73419: Image already exists
9e94b6f5e953: Image already exists
d834be925c79: Image already exists
4c115374adfc: Image successfully pushed
Digest: sha256:78d097eaded004cfa31252007533834beb6dd5b5d2d74f08b5b6a4574b79122d
nate@weyerbacher% docker push starforge/base-wheel:latest ~/git/starforge/wheels/image
The push refers to a repository [starforge/base-wheel] (len: 1)
8a40c04093cd: Image already exists
ee2d5171de71: Image successfully pushed
ee2d5171de71: Buffering to Disk
5b7a9e06dfda: Image successfully pushed
991a3085cc57: Image successfully pushed
d0e6975c75d2: Image successfully pushed
d0e6975c75d2: Buffering to Disk
11f17e6c581c: Image successfully pushed
134ff8959711: Image successfully pushed
134ff8959711: Buffering to Disk
b7336fb73419: Image already exists
9e94b6f5e953: Image already exists
d834be925c79: Image already exists
4c115374adfc: Image successfully pushed
Digest: sha256:b4d14a1f197898b0b78d401207d8b200e2a833b1e9070fb9e5a5ab7813fc2f22
```

No file, test, or entry point is named; start by locating the repository's Docker image build and push configuration, then trace how the listed image tags are generated. Done means the aliases no longer appear as separate Docker Hub images and do not require separate pushes.

Written by the indexing model from the issue text.