Refactor PR template: hint to curate packages around the submission

[oliverpool]

Hi, in #5224 I suggested that new Pull Requests should also check if the packages around the submission are still relevant.

I think this would allow to spread the load to check for older packages:

• spread over a larger number of people (since every user making a pull request should participate)
• spread over time for the maintainers (since every PR should only remove a couple of links, preventing stale issues because the numbers of links to check is very high)

I also took the liberty of moving some checkboxes around, to try to better categorize each step:

• read the guidelines
• ensure the submitted repo meets the quality standard
• links to the repo & services
• check of the pull-request content
• check of unmaintained packages around the submission

You can view an empty PR created with this new template at my fork: https://github.com/oliverpool/awesome-go/pull/2 Or see the pre-filled template when creating a PR: https://github.com/oliverpool/awesome-go/compare/main...patch-1

cc @phanirithvij

[github-actions[bot]]

Thank you for contributing to awesome-go. We will review your contribution as soon as possible.

Make sure you add the links in the body of the pull request that are requested in the contribution guide:

• repo link
• pkg.go.dev
• goreportcard.com
• coverage

Your project is under review. It may take a few days to be approved.