[Bug]: Badge Display Issue with Branch Names Containing URL-Unsafe Characters

[Bolero-fk]

What happened?

The issue arises when a branch name includes URL-unsafe characters, such as the hashtag (#). In these cases, the badge fails to display properly.

Steps to Reproduce:

1. Create or use a branch with a name that contains a URL-unsafe character (e.g., AddNewFeature#1).
2. Run the coverage-action workflow
3. Observe that the generated badges do not appear in the pull request comments as expected.

Additional Information:
I was able to display the badge correctly by manually changing the URL to encode the '#' character. For example, changing the URL from this:
![badge](<RepositoryName>/_xml_coverage_reports/data/AddNewFeature#1/badge.svg)
To this:
![badge](<RepositoryName>/_xml_coverage_reports/data/AddNewFeature%231/badge.svg)
This modification allowed the badge to be displayed as intended.

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct.

Contribution Guidelines

• I agree to follow this project's Contribution Guidelines.

Security Policy

• I agree to follow this project's Security Policy.

[cicdguy]

Thanks for the detailed report. We're looking into a fix for this. Will notify you when it's been released.

[cicdguy]

This should be fixed now @Bolero-fk
Related release: https://github.com/insightsengineering/coverage-action/releases/tag/v2.4.1