Flow future competencies into existing relevant competency sections

Why is this change being made?

This MR consolidates all competencies, whether yet supported or not, in to the relevant competency section for better navigation, consideration and discovery (less scrolling up/down a long page). It's still noted on the page that not all competencies are yet supported, and only the confirmed competencies have links to supporting docs. This MR also reduces redundancy by removing duplicate content that was previously mentioned twice, both in the competencies sections and in the future competencies section of the page.

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)