Add Control automation maturity section

Why is this change being made?

This MR updates the SecAssuranceAuto page with a few changes:

1. Update to the weighting of issues to use the fibonacci sequence scale to more closely align with Sec Auto. This comes out of a deeper dive into the usage of this scale and centers around complexity of problems not growing linearly but rather exponentially which is better represented by the fibonacci sequence. The qualitative definitions are not changing in this iteration.
2. Adding a Control Automation Maturity section and initial scale for use in assessing Control Automations. This also includes an explanation of how to use the scale. The reason for introducing the scale is that right now we don't have a standard scale to assess current/potential automation as it relates to controls and this will give us that capability which will help in prioritizing control automation work.
3. Additional minor changes to cleanup language and reflect more accurately current state.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

---