Set default token in cleanup-old-packages wrkflw

[ivanzati]

📝 Description

Test default token to delete package version workflow

✨ Type of Change

Select the type of change your PR introduces:

• [x ] 🐞 Bug fix – Non-breaking change which fixes an issue
• 🚀 New feature – Non-breaking change which adds functionality
• 🔨 Refactor – Non-breaking change which refactors the code base
• 💥 Breaking change – Changes that break existing functionality
• 📚 Documentation update
• 🔒 Security update
• 🧪 Tests

🧪 Testing Scenarios

Describe how the changes were tested and how reviewers can test them too:

• ✅ Tested manually
• 🤖 Run automated end-to-end tests

✅ Checklist

Before submitting the PR, ensure the following:

• 🔍 PR title is clear and meaningful
• ✍️ PR description clearly explains the changes and their reason
• 📝 I have linked the PR to the corresponding GitHub Issues, if any
• 💬 I have commented my code, especially in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ✅ I have added tests that prove my fix is effective or my feature works

[Copilot]

Pull Request Overview

This PR modifies the cleanup-old-packages workflow to use the default GITHUB_TOKEN instead of a custom GHCR_CLEANUP_TOKEN secret for package deletion operations. This change is being tested to verify if the default token has sufficient permissions for GitHub Container Registry cleanup tasks.

Key Changes:

• Replaced GHCR_CLEANUP_TOKEN with GITHUB_TOKEN across all cleanup operations
• Added error handling with continue-on-error: true to prevent workflow failures during testing

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[AlexanderBarabanov]

Could you please add a short inline comment here why do we need this permission - otherwise OpenSSF action will flag an issue (example - https://github.com/open-edge-platform/geti/security/code-scanning/204)

[ivanzati]

Thanks, have added inline comment