Migrate from DockerHub to GitHub Packages for future releases

Nobody has claimed this yet.

## Description

Migrate the rover Docker container distribution from DockerHub to GitHub Packages for future releases. This will centralize our container registry with our source code repository and provide better integration with GitHub workflows.

## Benefits

- **Centralized distribution**: Keep container images alongside source code
- **Better CI/CD integration**: Seamless integration with GitHub Actions
- **Access control**: Leverage GitHub's permission system for container access
- **Cost optimization**: Reduce dependency on external registries
- **Enhanced security**: Better vulnerability scanning and security features

## Tasks

- [ ] Set up GitHub Packages container registry for the repository
- [ ] Update CI/CD workflows to build and push to GitHub Packages
- [ ] Update documentation to reference new registry location
- [ ] Ensure backward compatibility during transition period
- [ ] Test container pull from GitHub Packages
- [ ] Update deployment scripts and references
- [ ] Communicate migration timeline to users

## Acceptance Criteria

- [ ] New releases are published to GitHub Packages
- [ ] CI/CD pipeline successfully builds and pushes to GitHub Packages
- [ ] Documentation is updated with new registry URLs
- [ ] Existing users can still access containers during transition

## Additional Context

This migration will improve our development workflow and align with GitHub's ecosystem. We should ensure proper versioning and tagging strategies are maintained during the migration.

Start by locating DockerHub references, CI/CD workflow definitions, deployment scripts, and documentation mentioned in the issue. Trace how images are built, tagged, published, and consumed, then test the transition and verify that new releases reach GitHub Packages while existing users retain access during migration.

Written by the indexing model from the issue text.