Add job scam warning to the new hire laptop ordering process

Why is this change being made?

We have an excellent and timely new blog post out: https://about.gitlab.com/blog/2023/06/29/fake-gitlab-job-scam/

It links to this page saying:

GitLab follows a published technology purchasing process, as outlined in our handbook, and won’t ask you to pay for technology equipment up front.

However the page does say:

If your country is not listed above or for any general laptop procurement questions please contact IT-Help@gitlab.com ▶ ▶ or your Candidate Experience Specialist to discuss alternate options. ◀ ◀

My concern is that someone who falls for a job scam may also fall for a scammer saying "Well, I'm your Candidate Experience Specialist, and the alternate option available to you is to send us $10,000 via payment-platform. Look, it says this can happen in the handbook!"

I added a warning panel to highlight the prevalence of fake job scams. https://about.gitlab.com/handbook/markdown-guide/#warnings

Relates to https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/34316+

TODO

• Can we be even more specific about our process? What are the "alternate options"?

Author Checklist

• 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
• 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.

---