Browser notifications don't correctly escape HTML

Summary

When I have an MR with <> in it, like "Something with std::unique_ptr<int>", it is escaped incorrectly in the Windows/Chrome browser notification popup when it changes status, so I see it as roughly "Something with std::unique_ptr & lt ; int & gt ;" in the popup window.

Steps to reproduce

Make an MR with <> in the title on Windows with Chrome, enable notifications, and kick off CI. Note that the popup shows raw HTML for the <>.

What is the current bug behavior?

The popup shows "Something with std::unique_ptr& lt ; int & gt ;" (except without the extra spaces -- I had to add them so this WYSIWYG Markdown entry window doesn't turn them into <>s.

What is the expected correct behavior?

The popup shows "Something with std::unique_ptr<int>".

Relevant logs and/or screenshots

I'll attach one if I catch it. The popup only stays for a moment.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

    (For installations with omnibus-gitlab package run and paste the output of: \\\\\\\\\\\\\\\`sudo gitlab-rake gitlab:env:info\\\\\\\\\\\\\\\`)  (For installations from source run and paste the output of: \\\\\\\\\\\\\\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\\\\\\\\\\\\\`)     

Results of GitLab application Check

Expand for output related to the GitLab application check

   (For installations with omnibus-gitlab package run and paste the output of: \\\\\\\`sudo gitlab-rake gitlab:check SANITIZE=true\\\\\\\`)  (For installations from source run and paste the output of: \\\\\\\`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\\\\\\\`)  (we will only investigate if the tests are passing)    

Possible fixes

Check with Little Bobby Tables. Fix the escaping.

Patch release information for backports

If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.

Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.

High-severity bug remediation

To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.