Addition of Pull Request template

[M-casado]

Summary

Added PR template

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New content (non-breaking change which adds new content)
• [ ] Modified content (non-breaking change which modifies existing content)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Motivation and Context

To provide a standard documentation upon the creation of a Pull Request in the GDI SOP GitHub repository.

References

ZenHub #258

Changes Introduced

• Added markdown PR template to .github

Review

No review yet.

Checklist:

General Compliance:

• [x] My changes follow the code style of this project (GDI SOP Style Guide) and the file naming conventions of the file accessioning proposal.
• [ ] I have verified that all new updated content is accessible, including checking that all external references are readable (i.e., no broken links). These may include references to external resources that should be resolvable, and internal references among SOPs.

Only applicable if the PR includes new, or changes to, GDI SOPs (i.e., documents at sops/):

• [ ] My SOP-related changes adhere to the Generic SOP Template, including format and required fields.
• [ ] I have consulted the Charter, ISM, and ORR documents to ensure compliance.
• [ ] I am complying with the established procedure for SOP creations and modifications, including respecting review phases and notifying needed contributors for reviews.

[M-casado]

Note: some links (e.g., the Charter, ISM, and ORR documents) are not resolvable yet, but will be when we create them. I preferred to add the final links rather than the Google Doc links.

[silviabah]

The PR template is complete as it is well documented and considers all the aspects that should be added when adding/modifying items to the GDI GitHub