feat(Obfuscation): add obfuscation guidelines

What does this MR do?

Email obfuscation came up in gitlab-org/gitlab!108901 (comment 1239082646) and it looks like it is a new pattern.

This MR documents the pattern decided so we can use it consistently across the product.

Want to use email obfuscation in code?

You can obfuscate emails from any place in the backend application with Gitlab::Utils::Email.obfuscated_email("see@me.com.uk", deform: true) (maybe , deform: true can be omitted when we decide we only want to have one version of email obfuscation).

Want to help document other obfuscation patterns?

Contribute to the follow up issue Improve obfuscation guidelines with further exa... (#1520)

Does this MR meet the acceptance criteria?

• The MR title and commit messages meet the Pajamas commit conventions.
• The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”.
  • For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
• Relevant label(s) are applied to the MR.
• The MR is added to a milestone.
• If creating a new component page from scratch, it follows the page template structure.
• Content follows the Pajamas voice and tone guidelines, falling back on the GitLab Documentation Style Guide when needed.
• Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter.
• If embedding a Figma file, it follows the Figma embed guide.
• Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.

Links