staging update of vrp-faq to reflect completed tracker migration

Change-Id: Iddc8d9b5f15aaada42071c84396da1d176ca140f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5265257
Reviewed-by: Alex Gough <ajgo@chromium.org>
Commit-Queue: Amy Ressler <amyressler@google.com>
Reviewed-by: Adrian Taylor <adetaylor@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1256003}

docs/security/vrp-faq.md

@@ -4,21 +4,18 @@
 
 ## News and Updates
 
-**Chromium is moving to a new issue tracker. Migration is scheduled to begin on
+**Chromium has migrated to a new issue tracker.** Please report all Chromium
-Friday, 2 February (17:00 PST) until some time by end of day PST Sunday, 4
+security bugs in the new tracker using [this
-February 2024.**
+form](https://issues.chromium.org/issues/new?noWizard=true&component=1363614&template=1922342).
-
-**As of 17:00 PST on Friday, 2 February, the legacy Chromium issue tracker,
-bugs.chromium.org, will be shifted to a read-only state. There will be no
-access to the [new issue tracker](https://issues.chromium.org) until the
-migration is complete on Sunday, 4 February.** If you have new security issues
-to report after the migration outage has begun, please report using the new
-issue tracker [bug reporting form](https://issues.chromium.org/new) once it is
-available when migration has been completed. Please reach out to
-security-vrp@chromium.org with any questions.
 
 Please check here for any news and updates about the Chrome VRP.
 
+* 4 February 2024: The Chromium issue tracker migration is now complete. Please
+  submit all issues using the [new issue tracker](https://issues.chromium.org)
+  and use [this
+  form](https://issues.chromium.org/issues/new?noWizard=true&component=1363614&template=1922342)
+  for directly reporting security issue to the security team.
+
 * 1 February 2024: Chromium issue tracker migration will begin on Friday, 2
   February 2024. During the migration new issues will not be able to be
   reported. As of 4 February 2024, all security bugs should be reported using
@@ -62,9 +59,8 @@ To help make the process of security bug triage as efficient and smooth as
 possible, please consider the following best practices for Chromium security bug
 reports:
 
-* Use the [bug reporting form](https://issues.chromium.org/new)
+* Use the [security bug reporting
-  for the Chromium bug tracker; select 'Security' from the "Which of the
+  form](https://issues.chromium.org/issues/new?noWizard=true&component=1363614&template=1922342)
-  following best describes the issue you are reporting?" dropdown.
   * This will allow the bug report to be included in the security bug triage
     queue immediately.
 * Include the version number and OS used to reproduce the bug. For an [extra