Deduplify content: Remove reviewee content from the review-guidelines

[castrojo]

reorganize pull request page.

The review-guidelines.md had duplicate content from pull-requests.md. I've removed it so that the review guidelines only have things useful to reviewers and pull-requests.md now has all the tips for getting a good review in one place.

The nitty gritty details of how prow/tide merges PRs is useful, but not so much when you're doing a PR, so I moved it to the bottom of the document so that the PR tips and best practices are listed before them.

And lastly I reformatted pull-requests.md to remove the confusing numerals (they'll look better in the ToC on the contributor site this way and also reformatted it with semantic line feeds, so sorry for the noise there.

Signed-off-by: Jorge O. Castro [email protected]

Which issue(s) this PR fixes:

fixes: #4444

[castrojo]

/assign mrbobbytables

[mrbobbytables]

A few changes and a few ideas, but overall does a good job of deduping 👍

[mrbobbytables]

/lgtm
/hold
For any other comments 👍
The other parts I specifically called out should be integrated can be done in a separate PR.

[parispittman]

it would be cool if the reviewer guidelines was turned into a checklist something like

• does it have tests
• can this be broken into multiple PRs

etc

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: castrojo, markyjackson-taulia

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• contributors/guide/OWNERS [castrojo]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mrbobbytables]

@parispittman there are a few items we want to add in a follow-up PR, would it be okay if those are added then?

[mrbobbytables]

discussed, we are good \o/ - changes will follow up in later PR.
/hold cancel