Shift focus from configuration to usage

Why is this change being made?

Many SCM features are very configurable, but the purpose of the features is not to increase the frequency that configuration is updated, but the frequency with which users get value.

Switching to a usage focus will encourage us to set great defaults, and minimize the amount of configuration. This is aligned to the FY22 goal of increasing adoption by improving usability.

Author Checklist

• Provided a concise title for the MR
• Added a description to this MR explaining the reasons for the proposed change, per say-why-not-just-what
• Assign this change to the correct 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 in 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.
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files. (this requirement has been removed pending identification of a new DRI for the handbook)