chore(PULL_REQUEST_TEMPLATE.md): add a pull request template to help guide users towards adhering to the AI policy

Author: aauren

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,67 @@
+<!--  Thanks for sending a pull request!  Here are some tips for you:
+
+1. If this is your first time, please read our contributor guidelines: https://github.com/cloudnativelabs/kube-router/blob/master/CONTRIBUTING.md and developer guide https://github.com/cloudnativelabs/kube-router/blob/master/docs/developing.md
+2. Ensure you have added or ran the appropriate tests for your PR: `make test` & `make lint`
+3. If the PR is unfinished, please mark it as a "Draft" when opening it
+-->
+
+#### What type of PR is this?
+
+<!--
+Please choose one of the following kinds:
+-->
+bug
+dependency
+cleanup
+documentation
+feature
+regression
+
+#### What this PR does / why we need it:
+
+#### Which issue(s) this PR is related to:
+<!--
+Please link relevant issues to help with tracking.
+
+To automatically close the linked issue(s) when this PR is merged,
+add the word "Fixes" before the issue number or link.
+-->
+
+#### Was AI used during the creation of this PR?
+<!--
+We are not against AI, but in the current era of tech AI is being used more and more to help upstream projects and it is
+useful for the maintainers of this project to understand if AI was used and to what extent it was used. Please see our
+AI policy: https://github.com/cloudnativelabs/kube-router/blob/master/AI_POLICY.md
+
+If no AI was used during the generation of this PR, please remove the following content and simply put "No" for this
+section.
+-->
+
+* What tool was used: <!-- One of Claude, Codex, Copilot, etc. -->
+* To what extent was the tool used? <!-- Anything from line autofill to it drafted the entire PR or anything imbetween -->
+* If drafted, how detailed of a plan did you create for the AI? <!-- Very detailed (multiple paragraphs) to not at all detailed (I gave it a single line prompt) -->
+* Help us understand if a human was in the loop or not for this PR? Yes or No
+
+#### What, if any, amount of integration testing was done with this change in a Kubernetes environment?
+<!--
+It is helpful for us to understand how much integration testing was done for this work. kube-router has extensive unit
+tests, but those only go so far for catching bugs that might turn up in an environment.
+
+Please let us know if you have done any tests beyond the unit tests that are required for validating your PR before
+submission. Responses for this section can range from: "I haven't done any integration tests" to "I deployed it in my
+environment of X number of nodes and exercised the functionality Y ways" to "I ran the entire Kubernetes Network
+validation suite against this change"
+-->
+
+#### Does this PR introduce a breaking change?
+<!--
+If no, just write "NONE" in the release-note block below.
+If yes, a release note is required:
+Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
+-->
+```release-note
+
+```
+
+#### Anything else the reviewer should know that wasn't already covered?
+