fix: update security.txt wording (#29973)

Fixup a missed mention of security@supabase.io and point everything to
Hackerone.

apps/docs/public/.well-known/security.txt

@@ -6,7 +6,9 @@ At Supabase, we consider the security of our systems a top priority. But no matt
 
 If you discover a vulnerability, we would like to know about it so we can take steps to address it as quickly as possible. We would like to ask you to help us better protect our clients and our systems.
 
-Out of scope vulnerabilities:
+The full scope of our VDP is available at https://hackerone.com/supabase.
+
+Here is a brief list of some common out of scope vulnerabilities:
 
 - Clickjacking on pages with no sensitive actions.
 - Unauthenticated/logout/login CSRF.
@@ -25,7 +27,7 @@ Testing guidelines:
 - Do not take advantage of the vulnerability or problem you have discovered, for example by downloading more data than necessary to demonstrate the vulnerability or deleting or modifying other people's data.
 
 Reporting guidelines:
-- E-mail your findings to security@supabase.io.
+- File a report through our VDP at https://hackerone.com/supabase
 - Do provide sufficient information to reproduce the problem, so we will be able to resolve it as quickly as possible.
 
 Disclosure guidelines:
@@ -36,7 +38,7 @@ Disclosure guidelines:
     - information about Supabase employees, contractors or partners
 
 What we promise:
-- We will respond to your report within 7 business days with our evaluation of the report and an expected resolution date.
+- We will respond to your report within 5 business days with our evaluation of the report and an expected resolution date.
 - If you have followed the instructions above, we will not take any legal action against you in regard to the report.
 - We will handle your report with strict confidentiality, and not pass on your personal details to third parties without your permission.
 - We will keep you informed of the progress towards resolving the problem.