Shorten PR checklist template

[vickyszuchin]

Issue description

Shorten PR checklist template. Review checklist and identify elements for removal to streamline the template for efficiency. However, we want

Acceptance criteria

• [ ] review checklist and identify elements for removal to streamline the template for efficiency
• [ ] discuss proposed updates to the checklist template with the team
• [ ] update checklist template
• [ ] Make a PR review section of our readmes that talks about our best practices and be sure to include the main steps of the current checklist (see additional context)

Additional context

When adding the PR review section to our readmes, this is to preserve our current best checklist for future developers that may onboard at another time. That said, you don't need repeat all the steps that duplicate for original developer, design reviewer and design reviewer Please wait until additional engineers/devs have onboarded, approximately July 2024.

Links to other issues

[vickyszuchin]

Per action item from eng huddle.

[PaulKuykendall]

https://github.com/weather-gov/weather.gov/pull/279#issuecomment-1759959083 has an interesting process.

[PaulKuykendall]

@abroddrick - please wordsmith this and move to Ready at your discretion.

[abroddrick]

Already did!

[rileyorr]

Hey all! Just dropping by to mention that I created a ticket to synthesize the accessibility survey findings that may influence some updates made to the PR checklist template as part of this ticket.

cc @gabydisarli @Katherine-Osos

[gabydisarli]

During our design sync on May 21st, we discussed introducing a new process for how we'll track when issues have bypassed the design phase. We decided that we should add an item to the PR checklist that has something along the lines of:

check with design to make sure the work to update the figma and content docs is documented (should only apply to issues with the "design-artifact-update" label.

cc: @vickyszuchin

[h-m-f-t]

I raised this higher in the backlog.