Chore: Make installers statically versioned

[stumpylog]

Proposed change

This PR isolates the building of the main image from changes to the installers until an update or change is wanted. This has the following benefits:

• An image will use a specific revision of the built installers for consistent building
  • Prevents things like [BUG] Last update of docker beta version not launching anymore #2056. If it worked once, it will always
• Installers include the versions of all installed packages when the build happened
  • helping determine why it changed, hopefully
• Caching should improve, as the installer image changes don't affect the main image anymore
• Installer images can be refined without affecting the main image
• Main image builds won't need to wait for installers (unless you're updating a version)

The flow isn't that much different than before.

1. The image builds a binary something (.deb, .whl, .so, etc)
2. The image lists out exactly what versions of what built the binary thing
3. New final job copies the binary thing into named, versioned, sorted directories, along with package versions info
4. The new job commits any changes to a special branch and pushes

The building of the main image changed a bit, but honestly not that much either.

1. Versions are still provided via build arguments
2. RUN step curls the repository at a given revision which exists only on the binaries branch
3. the build binary items are installed or copied into location

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain) - getting towards reproducible builds

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[coveralls]

Pull Request Test Coverage Report for Build 4016649303

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.03%) to 92.74%

---

Totals
Change from base Build 4012284681:	0.03%
Covered Lines:	5557
Relevant Lines:	5992

---

💛 - Coveralls

[shamoon]

I cant provide meaningful feedback on the code but the motivation seems great and clearly I think we all have trust in your handling of the ci side so I see no issue in merging especially into dev. Again, unless of course you need more specific input

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.