Simplify the OSM release guide

[jaellio]

Please describe what should be documented

The release_guide.md has a very dense instruction set. The release guide should be easy to follow and understand. I suggest breaking up the release guide into several documents. For example, pre-release checklist, release candidates, release, and announcements.

The main goal is to simplify the release process to reduce and clarify the work required of the release manager. The release guide does not need to be broken up exactly like I suggested above.

Please suggest where in the repo the document should be located

If multiple release guides are created they could be added to a new folder under /docs.

[github-actions]

Added default label size/needed. Please consider re-labeling this issue appropriately.

[github-actions]

Added default label kind/needed. Please consider re-labeling this issue appropriately.

[phillipgibson]

The OSM project has been officially archived by the CNCF. There will be no more new development on any repo under the OpenServiceMesh organization.