fix: release process runs twice

[project-defiant]

✨ Context

This PR refers to the opentargets/issues#3673.

🛠 What does this PR implement

There were two causes to run twice the downstream jobs on release process was

• bug in how the if condition was evaluated - the value of the if: ${{ steps.semrelease.outputs.released }} == 'true' did not evaluate correctly
• downstream jobs (publish to pypi and documentation) were not conditionally triggered by the output of semrelease

Additionally, as we do not use the release** branches, I changed the requirement to publish-to-testpypi to run on main branch (as a test before the actual pypi release)

🙈 Missing

🚦 Before submitting

• Do these changes cover one single feature (one change at a time)?
• Did you read the contributor guideline?
• Did you make sure to update the documentation with your changes?
• Did you make sure there is no commented out code in this PR?
• Did you follow conventional commits standards in PR title and commit messages?
• Did you make sure the branch is up-to-date with the dev branch?
• Did you write any new necessary tests?
• Did you make sure the changes pass local tests (make test)?
• Did you make sure the changes pass pre-commit rules (e.g poetry run pre-commit run --all-files)?

[ireneisdoomed]

Thank you for the fixes. Just one Q about the pypy test workflow, are we publishing to Pypy and Tespypy at the same time (after the commit to main)? If so, what is the value of publishing to different repositories at the same time?

[ireneisdoomed]

Got it now!
The process is:

• allow to publish to TestPypy
• test the package
• allow to publish to Pypy
• 🥳