Remove - open application page from HB

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

We have had a few questions come through from people inquiring about open applications due to this HB page. It creates a sub-par experience and sets unrealistic expectations from the talent community in that we do not currently have opportunistic hiring efforts at GitLab and there is no avenue to 'apply' to this position. We do have talent communities in our CRM that we would rather direct people to in order to get involved when we do not have a open role for them to apply for. We'd like to remove this HB page to better align to the process we have to date and the experience we provide to candidates and prospects alike.

@drogozinski I am not entirely sure how to delete an entire handbook page - so might need your help on that in this MR. I've already ran by @rallen3 and he is comfortable with our decision to sunset this page.

cc: @jconnors3 @jakefoster1 @Mjubrey

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

CHANGEME

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

Commits

• Update file index.html.md

---