Rename Sitespeed urls that moved from Editor to Source Code
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=402752) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=402752) </details> <!--IssueSummary end--> <!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Some urls being tracked in our sitespeed-measurement-setup are labeled as belonging to Editor but have moved to the domain of Create:Source Code. * `Editor_Snippets_Explore` * `Editor_Snippet_Dashboard` * `Editor_SingleFile_team_page` * `Editor_Snippet_new` * `Editor_Snippets_Textual` * `Editor_Snippets_Multifile` * `Editor_Snippets_Markdown` [Dashboard](https://dashboards.gitlab.net/d/sftijGFMz/sitespeed-lcp-leaderboard?orgId=1&refresh=5m&var-namespace=sitespeed_io&var-path=desktop&var-testname=gitlab&var-domains=gitlab_com&var-pages=Editor_SingleFile_team_page&var-pages=Editor_Snippet_Dashboard&var-pages=Editor_Snippet_new&var-pages=Editor_Snippets_Explore&var-pages=Editor_Snippets_Markdown&var-pages=Editor_Snippets_Multifile&var-pages=Editor_Snippets_Textual&var-pages=SourceCode_Blob_View_Large&var-pages=SourceCode_Blob_View_Refactor_Disabled&var-pages=SourceCode_Blob_View_Refactor_Enabled&var-pages=SourceCode_Blob_View_Small&var-pages=SourceCode_DeepDirectoryView&var-pages=SourceCode_File_Blame_Large&var-pages=SourceCode_File_Blame_Small&var-pages=SourceCode_HighlightJs__Enabled&var-pages=SourceCode_Repo_Large&var-pages=SourceCode_Repo_Small&var-browser=chrome&var-function=median&var-connectivity=cable) <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->
issue