Update pull_request_template.md to include testing instructions for changes to dbt models

[evansiroky]

Description

Include additional guidance on how to test changes made to dbt models.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

How has this been tested?

N/A

Post-merge follow-ups

Document any actions that must be taken post-merge to deploy or otherwise implement the changes in this PR (for example, running a full refresh of some incremental model in dbt). If these actions will take more than a few hours after the merge or if they will be completed by someone other than the PR author, please create a dedicated follow-up issue and link it here to track resolution.

• No action required
• Actions required (specified below)

Make announcement in change in procedure to slack.

[vevetron]

I Agree.

[erikamov]

I was already using this command to make sure the model can be successfully created and works on Staging and mentioning the staging model name on my PRs to help the approval process.
Adding the log in PRs sounds easy enough and it is a good way to make sure that was tested.