Increase Privacy and Security Visibility

I noticed there are times when some privacy/security concerns aren't mentioned from reviewers till the i2e or i2s stage. From my own analysis, this usually doesn't cause major delays, but in a smaller number of cases, it has. One idea to help is to include a section on privacy and security considerations in the i2p emails to get more eyes on these at an earlier stage. More specifically, include privacy/security considerations in an earlier section of ChromeStatus and have it included in the template for an i2p. I also noticed that ChromeStatus has a section for "Security risks" but not privacy. At the minimum, I think it would be helpful to have a separate section for privacy, as well, since based on my analysis, the most frequent kind of privacy/security consideration brought up during the i2s or i2e stage from reviewers was fingerprinting, so this could potentially help feature owners start thinking through these sorts of questions at an earlier stage, and provide API Owners with more data during their reviews.