fix: dev release process

[project-defiant]

✨ Context

This PR performs maintnance over the github actions after last release (v2.1.0)

🛠 What does this PR implement

• Simplification over the actions usage (skip the name to the step parameter if the action name is descriptive enough)
• Adds possibility to tag with vX.Y.Z-dev.V version triggered only from the dev branch and manual workflow
• Removes the github app token, as we no need it - the release action is run from the main branch, does not have to be triggered by the another workflow
• PyPI deployment now requires TestPyPI to deploy successfully
• new python versions allowed to bump the version of python-semantic-release, this include:
  • Swap of the deprecated python-semantic-release/upload-to-gh-release action for python-semantic-release/[email protected] to match the latest python-semantic-release/python-semantic-release action
  • Configuration changes for the changelog with latest python-semantic-release/python-semantic-release actions.
• Documentation update on how the development process should loook like.

🙈 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 uv run pre-commit run --all-files)?