update documentation to more clearly discourage use of this plugin

this plugin works great for release workflows that truly need to make commits during the release process, but we want to make it more clear to users that enables releases without the need to make commits. this is the reason why this plugin in not included by default in the core package:

• some users overvalue having the current version number in the source code repository. semantic-release does not use this value to track the previous version, instead it uses tags. instead it is better to refer to the package registry as the source of truth for which version is currently latest (for example, with npm, npm dist-tags ls is a great way to get this information)
• some users value maintaining a CHANGELOG.md file over using, for example, github releases. the changelog plugin is also not included by default in the core package to encourage folks to leverage alternatives to maintaining a CHANGELOG file

including commits as part of the release process adds complexities like:

• working through access issues for pushing commits to release branches with restrictive branch protection rules
• pulling release commits before being able to push additional changes to the release branch
• releasing multiple packages from the same repository (officially unsupported by semantic-release) is prevented because the commit resulting from the release of the first package puts the repo in a state where it is behind the latest commit when attempting to release the remaining packages

No file or test is named in the issue. Locate the plugin documentation describing release commits, revise it to discourage unnecessary commits and explain the registry, tags, GitHub Releases, and commit-related constraints, then verify the documentation reflects the requested guidance.