apacheGH-15249: [Documentation] Add PR template (apache#15250)

* Closes: apache#15249

Lead-authored-by: Jacob Wujciak-Jens <jacob@wujciak.de>
Co-authored-by: David Li <li.davidm96@gmail.com>
Signed-off-by: Yibo Cai <yibo.cai@arm.com>

.github/pull_request_template.md

@@ -0,0 +1,62 @@
+# Which issue does this PR close?
+
+<!--
+Thanks for opening a pull request!
+If this is your first pull request you can find detailed information on how 
+to contribute here:
+  * [New Contributor's Guide](https://arrow.apache.org/docs/dev/developers/guide/step_by_step/pr_lifecycle.html#reviews-and-merge-of-the-pull-request)
+  * [Contributing Overview](https://arrow.apache.org/docs/dev/developers/overview.html)
+
+
+If this is not a [minor PR](https://github.com/apache/arrow/blob/master/CONTRIBUTING.md#Minor-Fixes). Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose
+
+Opening GitHub issues ahead of time contributes to the [Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.) of the Apache Arrow project.
+
+Then could you also rename the pull request title in the following format?
+
+    GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
+
+or
+
+    MINOR: [${COMPONENT}] ${SUMMARY}
+
+In the case of old issues on JIRA the title also supports:
+
+    ARROW-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
+    PARQUET-${JIRA_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
+
+-->
+Closes #
+
+# Rationale for this change
+
+<!--
+ Why are you proposing this change? If this is already explained clearly in the issue then this section is not needed.
+ Explaining clearly why changes are proposed helps reviewers understand your changes and offer better suggestions for fixes.  
+-->
+
+# What changes are included in this PR?
+
+<!--
+There is no need to duplicate the description in the issue here but it is sometimes worth providing a summary of the individual changes in this PR.
+-->
+
+# Are these changes tested?
+
+<!--
+We typically require tests for all PRs in order to:
+1. Prevent the code from being accidentally broken by subsequent changes
+2. Serve as another way to document the expected behavior of the code
+
+If tests are not included in your PR, please explain why (for example, are they covered by existing tests)?
+-->
+
+# Are there any user-facing changes?
+
+<!--
+If there are user-facing changes then we may require documentation to be updated before approving the PR.
+-->
+
+<!--
+If there are any breaking changes to public APIs, please add the `breaking-change` label.
+-->

dev/release/rat_exclude_files.txt

@@ -214,3 +214,4 @@ r/inst/include/cpp11/*.hpp
 r/tools/nixlibs-allowlist.txt
 .gitattributes
 ruby/red-arrow/.yardopts
+.github/pull_request_template.md