chore: update SECURITY.md

Switching security@ back to legacy .io until we have .tech set up

SECURITY.md

@@ -6,7 +6,7 @@ The IPFS protocol and its implementations are in varying but active levels of de
 
 If you find a vulnerability that may affect live deployments -- for example, expose a remote execution exploit -- please send your report privately to either:
 1. The implementation team if its an issue with a particular implementation OR
-2. security@ipfs.tech if you're not sure or if its an underlying issue with an IPFS protocol.
+2. security@ipfs.io if you're not sure or if its an underlying issue with an IPFS protocol.
 Please DO NOT file a public issue.
 
 If the issue is a protocol weakness or something not yet deployed, just discuss it openly.