Migrate repos to shared-workflows for CI/CD

[mairas]

Summary

Migrate all repositories using the pr-main-release CI/CD pattern to use the centralized hatlabs/shared-workflows reusable workflows.

Background

We've created hatlabs/shared-workflows to centralize the pr-main-release CI/CD logic. This eliminates duplicated workflow code across repos and makes maintenance easier.

Reference PR: halos-org/cockpit-apt#107 (successfully merged and tested)

Repos to Migrate

halos-distro workspace

• cockpit-apt - PR bug: HOSTNAME inherits the host's name under network_mode: host, breaking container self-inspection #107 merged, working
• halos-metapackages - Migrate to shared-workflows for CI/CD halos-metapackages#4
• halos-marine-containers - Migrate to shared-workflows for CI/CD halos-marine-containers#28
• container-packaging-tools - Migrate to shared-workflows for CI/CD container-packaging-tools#68
• cockpit-dockermanager-debian - Migrate to shared-workflows for CI/CD cockpit-dockermanager-debian#10

HALPI2 repos

• HALPI2-rust-daemon - Migrate to shared-workflows for CI/CD hatlabs/HALPI2-rust-daemon#75
• HALPI2-firmware - Migrate to shared-workflows for CI/CD hatlabs/HALPI2-firmware#24
• HALPI2-daemon - Migrate to shared-workflows for CI/CD hatlabs/HALPI2-python-daemon#37

Migration Steps per Repo

1. Create feature branch feat/use-shared-workflows
2. Replace workflow files with thin callers (see shared-workflows README)
3. Keep local scripts if needed (multi-package repos)
4. Test PR checks pass
5. Merge and verify full release cycle works

Benefits

• Before: ~300 lines of workflow code per repo
• After: ~40 lines per repo
• Single source of truth for CI/CD logic
• Easier to update release process across all repos

Documentation

• shared-workflows README
• Local script overrides