Update the job family specialities with separate specialities for Distribution Build

Why is this change being made?

Update Job Family specialities for Build vs Deploy teams. One of the advantages of having the two teams is to be able to target a more narrow set of skills which we think might appeal to more candidates. (Job Famililies are the basis starting point of our Job postings)

My focus here was mostly on the Build team, but where I pulled information from existing places for the Build team, I did the same for the Deploy team.

So I:

• Updates the descriptions of the team with information from the charters: https://about.gitlab.com/handbook/engineering/development/enablement/distribution/#distributionbuild-charter
• Listed the responsibilities, copied from: https://about.gitlab.com/handbook/engineering/development/enablement/distribution/#distribution-build
• Updated some of the requirements, mostly just bringing in from the seperate cloud-native job family. Otherwise mostly kept the requirements similar, just splitting build verabage from deploy/configure verbage.

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
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this change to the correct DRI(s)
  • 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 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.

---