pr: Update Github PR template

AI-Assisted: no

Author: gpotter2

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,24 +1,25 @@
-<!-- This is a checklist of actions required to have a PR reviewed. You should include it and fill it accordingly. (You may only remove it if you check all items and you are a well-known contributor.) -->
+<!-- Hi there ! First of all thanks a lot for contributing to Scapy ! We're really grateful for contributions and for the time people spend contributing back. Please note that due to the amount of contributions, we have to impose quality standards for PRs.
 
-**Checklist :**
+Here is a small checklist of actions to get you started with this PR. You may remove this entire section once you're done. Please note that if you don't follow the guidelines detailed here, we might end up closing the PR :( When in doubt, ask !
 
--   [ ] If you are new to Scapy: I have checked [CONTRIBUTING.md](https://github.com/secdev/scapy/blob/master/CONTRIBUTING.md) (esp. section submitting-pull-requests)
--   [ ] I squashed commits belonging together
--   [ ] I added unit tests or explained why they are not relevant
--   [ ] I executed the regression tests (using `tox`)
--   [ ] If the PR is still not finished, please create a [Draft Pull Request](https://github.blog/2019-02-14-introducing-draft-pull-requests/)
--   [ ] This PR uses (partially) AI-generated code. If so:
-    - [ ] I ensured the generated code follows the internal concepts of scapy
-    - [ ] This PR has a test coverage > 90%
-    - [ ] I reviewed every generated line
-    - [ ] If this PR contains more than 500 lines of code (excluding unit tests) I considered splitting this PR.
-     - [ ] I considered interoperability tests with existing packages or utilities to ensure conformity of a newly generated protocol
+Checklist :
 
-**I understand that failing to mention the use of AI may result in a ban. (We do not forbid it, but you must play fair. Be warned !)**
+- Check the contribution guide at https://github.com/secdev/scapy/blob/master/CONTRIBUTING.md (esp. section submitting-pull-requests)
+- Have good commit hygiene. They must have the `AI-Assisted` tag as explained in the contributing guide. Please squash commits that belong together, and split commits that contain multiple features.
+- AI: You must make sure that you understood the internal concepts of Scapy and have good test coverage (like >90%). Please review ALL the code you generated.
+- Add unit tests or explain why they are not relevant.
+- If the PR is still not finished, please create a **Draft Pull Request**
+- If this PR contains more than 500 lines of code (excluding unit tests), consider splitting it.
+- New protocols: I considered interoperability tests with existing packages or utilities to ensure conformity of a newly generated protocol
+
+Please read the output of the tests if they fail ! In rare cases, some tests might fail for reasons unrelated to your PR, sorry about that ! Just explain it and we'll relaunch them.
+-->
+
+### Description
 
 <!-- brief description what this PR will do, e.g. fixes broken dissection of XXX -->
 
-<!-- if required - short explanation why you fixed something in a way that may look more complicated as it actually is ->>
+<!-- if required - short explanation why you fixed something in a way that may look more complicated as it actually is -->
 
 <!-- if required - outline impacts on other parts of the library -->