[Doc] Move PR template content to docs

[russellb]

b87d45d [CI/Build] Expand PR body cleanup to catch another pattern
d1cf025 [Doc] Move pr template content to docs

commit b87d45d
Author: Russell Bryant rbryant@redhat.com
Date: Fri Nov 8 08:38:40 2024 -0500

[CI/Build] Expand PR body cleanup to catch another pattern

In a recent PR, I saw another pattern that is probably common, but
wasn't handled by this script. All of the template was removed except
for the section that has the "click to expand" header.

Signed-off-by: Russell Bryant <rbryant@redhat.com>

commit d1cf025
Author: Russell Bryant rbryant@redhat.com
Date: Fri Nov 8 09:24:39 2024 -0500

[Doc] Move pr template content to docs

Move the bulk of the content from the PR template to the contributing
section of the docs.

Signed-off-by: Russell Bryant <rbryant@redhat.com>

[github-actions]

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

• Add ready label to the PR
• Enable auto-merge.

🚀

[DarkLight1337]

LGTM, though @simon-mo should make the final decision on this since it affects the PR template.

[DarkLight1337]

@simon-mo quick ping in case you missed it.

[njhill]

I am in favour of this!