Update Release Process Doc to Include New Process

[CloudBeard]

Describe what should be investigated or refactored

Update the release-process.md inside of docs to include a newer steps and frequency on how the Lula team releases versions.

Newer steps/process to add below:
Ownership of the release will be rotated week by week for each person on the team.

Release Owner is expected to Review the release please pr prior to the Friday sync session and provide a recommendation for release or not release based on the following:

• Current State of the release please pr
• Inclusion of Meaningful updates (deps, fix, features etc)
• Any blocking issue/PR that should be evaluated

If releasing - the release owner should notify the team, add a milestone to the PR to kickoff the workflows, and await 2x reviews on the release please pr prior to merge.

Release Owner will monitor the tag/release-draft creation and add a small summary to the release draft.

At the Sync Meeting - the team will review the draft and collectively agree on publishing as latest release.

Links to any relevant code

https://github.com/defenseunicorns/lula/blob/main/docs/community-and-contribution/release-process.md

[brandtkeller]

I'd like to reframe the updates around:

• Update the release process to include steps not currently documented - without a focus on the ownership role of release.
• Update the process to reflect removing the quality gate of review required to publish a draft release after a human-friendly summary has been added.