Doc: Update PR template checklist

[mariana-caetano]

What's the purpose of this pull request?

Added new items to the pull_request_template.md to help highlight the changes added in the CHANGELOG.md and Release Notes.

How does it work?

The new items intended to help users and the team identify the changes in gatsby.store and keep a pattern in the CHANGELOG.md update.

Checklist Item	Before	Now
CHANGELOG entry added	✅	✅
Added an entry in the CHANGELOG.md at the beginning of its due section. The latest version should comes first.	❌	✅
Added the PR number with the PR link at the entry in the CHANGELOG.md	❌	✅
Updated the Storybook - if applicable.	❌	✅
Added a label according to the PR goal - Breaking change, Enhancement, Bug or Chore.	❌	✅
Added the component, hook, or pathname in-between backticks (``) - If applicable. E.g., ComponentName component.	❌	✅
Identified the function or parameter in the PR - If applicable. E.g., useWindowDimensions hook.	❌	✅
For documentation changes, ping @ carolinamenezes or @ Mariana-Caetano to review and update the changes.	❌	✅

How to test it?

Describe the steps with bullet points. Is there any external reference, link, or example?

References

• Keep a changelog
• Pull Request best practices

Checklist

You may erase this after checking them all ;)

• CHANGELOG entry added

[vtex-sites]

Preview is ready

This pull request generated a Preview

👀   Preview: https://preview-12--gatsby.preview.vtex.app
🔬   Go deeper by inspecting the Build Logs
📝   based on commit c5c6668

[vtex-sites]

Lighthouse Reports

Here are the Lighthouse reports of this Pull Request

Page	Report
/	📎   Access the Lighthouse report here.
/apple-magic-mouse-99988212/p	📎   Access the Lighthouse report here.
/office	📎   Access the Lighthouse report here.

[filipewl]

Thanks!

[filipewl]

Oooh, good call adding the link! Hadn't noticed GH didn't create the link automatically as it does inside issues and PRs messages. Will do the same moving forward.
😬

[mariana-caetano]

Yes! 😃 I will add this to the checklist as well!

[filipewl]

Added these 2 missing labels to the repo:

[mariana-caetano]

Thanks, @filipewl!

[filipewl]

For some unknown reason, the last commit didn't seem to trigger our WebOps checks on GH... You may need to push an empty commit to trigger a new attempt (e.g. git commit -m 'Trigger CI with an empty commit' --allow-empty --no-verify && git push).

---

Edit: the new commit has started a new attempt already!

[heitorado]

Looking good :)