[Bug]: Release workflows should make PRs instead of pushing to `master`

[yardasol]

Expected behavior

The next-release-minor.yml workflow should pass

Describe the bug

The next-release-minor.yml workflow fails becasue it tries to push file changes directly to master. This causes the workflow to fail since master is a protected branch and changes requires an approving review from users with write access.

To Reproduce

Steps to reproduce the behavior:

1. Look at this action report

System Specifications:

• Software version: SaltProc v0.3.0
• Subsystem: Github actions

How can this issue be closed?

This issue can be closed when the next-release-minor workflow is changed to do the following.

Create a PR with the following changes:

• A release notes file for the new version
• Update the version number(s) in version.py
• Remove the "in-development" note from the release notes for the current release.

[yardasol]

The implementation in # 136 works for the most part, however looking at the workflow log, we can see that one of the PRs fails to be created:

  CONFLICT (modify/delete): doc/releasenotes/v0.5.0.rst deleted in HEAD and modified in 4373343 (final changes before publishing v0.5.0). Version 4373343 (final changes before publishing v0.5.0) of doc/releasenotes/v0.5.0.rst left in tree.
  error: could not apply 4373343... final changes before publishing v0.5.0
  hint: After resolving the conflicts, mark them with
  hint: "git add/rm <pathspec>", then run
  hint: "git cherry-pick --continue".
  hint: You can instead skip this commit with "git cherry-pick --skip".
  hint: To abort and get back to the state before "git cherry-pick",
  hint: run "git cherry-pick --abort".
  Error: Unexpected error: error: could not apply 4373343... final changes before publishing v0.5.0
  hint: After resolving the conflicts, mark them with
  hint: "git add/rm <pathspec>", then run
  hint: "git cherry-pick --continue".
  hint: You can instead skip this commit with "git cherry-pick --skip".
  hint: To abort and get back to the state before "git cherry-pick",
  hint: run "git cherry-pick --abort".

I'm reopening this issue. It can be closed when this behavior is fixed.