Fix `bump-version` CI workflow

[RRosio]

• Workflow to bump version, commit and push along with tags is failing, even with authorized (Bypassing restrictions and requirements) github actor (https://github.com/fsspec/jupyter-fsspec/actions/runs/12308858186/job/34354926891)

remote: error: GH006: Protected branch update failed for refs/heads/main.        
remote: 
remote: - Changes must be made through a pull request.        
remote: 
remote: - You're not authorized to push to this branch. Visit https://docs.github.com/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches for more information.        
To https://github.com/fsspec/jupyter-fsspec
 ! [remote rejected] main -> main (protected branch hook declined)
error: failed to push some refs to 'https://github.com/fsspec/jupyter-fsspec'
Error: Failed to push changes. Check repo permissions.

• Remove environment for workflow (causes it to appear as a deployment)

[RRosio]

Reference:

• https://github.com/orgs/community/discussions/25305
• https://github.com/orgs/community/discussions/13836
  • deploy key (see https://github.com/orgs/community/discussions/25305#discussioncomment-10728028)

Consider:

• https://jupyter-releaser.readthedocs.io/en/latest/how_to_guides/convert_repo_from_repo.html#checklist-for-adoption
  • Github App at an individual level => tied to a user only not helpful
  • Github App at the org level => tied to the org

[RRosio]

We can try the deploy key (note the Github message: "We recommend using GitHub Apps instead for fine grained control over repositories and enhanced security.")
Then we would still be relying on granting the deploy key bypass for branch protection rules and requirements. I've tried doing this with the github actor but the workflow does not seem able to bypass those rules... there is likely some misalignment there.