doc: ping nodejs/tsc for each security pull request

Refs: nodejs/TSC#1687 PR-URL: #57309 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>

Author: RafaelGSS

doc/contributing/security-release-process.md

@@ -56,6 +56,9 @@ The current security stewards are documented in the main Node.js
  * Use the "summary" feature in HackerOne. Example [2038134](https://hackerone.com/reports/2038134)
  * `git node security --add-report=report_id`
  * `git node security --remove-report=report_id`
+ * Ensure to ping the Node.js TSC team for review of the PRs prior to the release date.
+ * Adding individuals with expertise in the report topic is also a viable option if
+ communicated properly with nodejs/security and TSC.
 
 * [ ] 3\. **Assigning Severity and Writing Team Summary:**
  * [ ] Assign a severity and write a team summary on HackerOne for the reports