fix: CHANGELOG contains stale GitLab commit URLs after migration to GitHub

Problem

After migrating from GitLab to GitHub, CHANGELOG.md still references commit hashes as links pointing to gitlab.consulting.redhat.com. These links are inaccessible from the public GitHub repository and mislead contributors trying to trace changes.

Example from CHANGELOG.md:

([`7db166a`](https://gitlab.consulting.redhat.com/redhat-cop/openshift-virtualization-migration/openshift_virtualization_migration_ees/-/commit/7db166a...))

Proposed Solution

Update historical CHANGELOG.md commit links from gitlab.consulting.redhat.com/... to the equivalent GitHub URLs:
https://github.com/redhat-cop/openshift_virtualization_migration_ees/commit/<hash>

Going forward, ensure pyproject.toml is configured to generate GitHub-native commit links via python-semantic-release.

Files to Change

• CHANGELOG.md
• pyproject.toml (verify [tool.semantic_release.remote] section points to GitHub)

Start by searching CHANGELOG.md for gitlab.consulting.redhat.com links and inspect the [tool.semantic_release.remote] section in pyproject.toml. Update the historical links to the specified GitHub commit format and verify the semantic-release remote points to GitHub; done means no stale GitLab commit URLs remain.