[8.14] ci(release): update descriptions and use oblt-actions@v1 (backport #13529)

[mergify]

Motivation/summary

• Use v1 version for oblt-actions
• Use oblt-actions rather than apm-pipeline-library <-- it's now deprecated
• Update the description so it explicitly explains the expected input parameter.

The release.mk is the one in charge of doing the auto-bump:

• for the patch release:

  apm-server/release.mk

  Line 45 in 0e77c56

  NEXT_RELEASE ?= $(RELEASE_BRANCH).$(shell expr $(PROJECT_PATCH_VERSION) + 1)

• for the minor release:

  apm-server/release.mk

  Line 44 in 0e77c56

  NEXT_PROJECT_MINOR_VERSION ?= $(PROJECT_MAJOR_VERSION).$(shell expr $(PROJECT_MINOR_VERSION) + 1).0

Further details

• .github/workflows/run-patch-release.yml should be run using the main branch and the version to be released.
• .github/workflows/run-minor-release.yml should be run using the main branch and the current version in main.

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Related issues

---

This is an automatic backport of pull request #13529 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of daf2ef9 has failed:

On branch mergify/bp/8.14/pr-13529
Your branch is up to date with 'origin/8.14'.

You are currently cherry-picking commit daf2ef90d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   .github/workflows/prepare-release/action.yml
	modified:   .github/workflows/run-minor-release.yml

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/run-patch-release.yml
	both modified:   dev_docs/RELEASES.md

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally