Clarifying Questions and Feedback on StORM hb page

Why is this change being made?

To track comments and questions from @madlake during her SecRisk shadow. In addition to answering @madlake's questions, we also took this opportunity to refresh our documentation to more closely align with current practices and direction. The following changes were made as a result of this MR:

1. Combined guidance from the to-be-deleted StORM Methodology with the StORM Program handbook page for easy reference and avoid having to flip back and fourth between the two (efficiency).
2. We moved the System Intake Process to the SEC-Controls Handbook page as it is a process which feeds into Security Compliance's audit plan.
3. We incorporated the Making Decisions Handbook page closing https://gitlab.com/gitlab-com/gl-security/security-assurance/security-risk-team/storm/-/issues/399+
4. Reflecting our move from annual reporting to quarterly reporting closing https://gitlab.com/gitlab-com/gl-security/security-assurance/security-risk-team/storm/-/issues/431+
5. Moved away from references of Tier 1 (ERM risks), 2 (StORM risks), 3 (security compliance observations), risks/observations and called them by their name for transparency
6. Acknowledgement of subjectivity of risk scoring and our mitigating response.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---