Updating release docs to make it clear that it's ok to merge your own individual package release PRs (open-telemetry#3872)

Author: aabmass

RELEASING.md

@@ -37,6 +37,7 @@ to pick a specific package to release. It follows the same versioning strategy a
 Long-term package release branch follows `package-release/{package-name}/v{major}.{minor}.x` (or `package-release/{package-name}/v{major}.{minor}bx`) naming pattern.
 
 The workflow will create two pull requests, one against the `main` and one against the `package-release/` branch; both should be merged in order to proceed with the release.
+To keep the process lightweight, it's OK to approve the PRs you generate and merge without additional reviews.
 
 ## Preparing a new patch release