ci(containers): use RELEASE_TOKEN for releases

[suchapalaver]

This PR updates the CI release workflow to use a RELEASE_TOKEN secret instead of the default GITHUB_TOKEN. The default token cannot trigger workflows that are defined as reusable or that call other actions due to GitHub’s security restrictions. The RELEASE_TOKEN is a personal access token with appropriate scopes, enabling the release workflow to trigger dependent workflows such as Docker image publishing or changelog generation.

[coveralls]

Pull Request Test Coverage Report for Build 15716426453

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.008%) to 72.414%

---

Files with Coverage Reduction	New Missed Lines	%
crates/tap-agent/src/agent/sender_account.rs	1	77.25%

Totals
Change from base Build 15683389886:	-0.008%
Covered Lines:	8812
Relevant Lines:	12169

---

💛 - Coveralls