Add translation context to "Pages" string in Drupal Canvas

Overview

Hello dear Drupal community. I would like to take this opportunity to update the issue summary again, because I tried earlier to have the AI write a clean issue. That went completely wrong.

In Drupal CMS 2.0, there is a new menu item on the left side of the Administration menu. It is called Current Pages. Behind it is the new Canvas module.

The name is not wrong. But it does not distinguish between normal content, as listed under Content (Node Module), and pages built with Canvas.
If you are not familiar with Drupal, then the person who wants to learn Drupal needs to know the difference between a page that I build with Canvas and a page that I create under Content. Drupal CMS, or rather the Canvas module, does not explain this anywhere in the UI.
However, this leads to massive confusion among users in languages such as German. This is mainly because we currently make no distinction in the UI between whether we create pages with the Node module or with Canvas. According to the official style guide, we officially refer to content or content items. See: https://www.drupal.org/docs/develop/user-interface-standards/interface-t.... That alone makes it difficult. Formulating clear interface texts. Now, in the navigation, we suddenly talk about pages (Canvas) and content (Node Module), which we have used to create content such as basic pages up to now. And now the navigation suddenly talks about pages, content, and utility pages.
That doesn't really make it any easier to correctly identify who's who in the entity jungle. Especially if you're not a developer and just want to create websites.

To avoid any confusion in our communication, my suggestion for the string in the UI that currently represents the word “pages” is to simply create a context. This way, we can refer to Canvas as Canvas Pages. At the very least, this makes it clearer which Drupal component is currently being used.

We don't have to rush into this, but we should make the decision by the time the recipes are finally ready to be translated, so that we can provide users with the correct information at that point. Perhaps this is simply a puzzle for the documentation team and a corresponding section in the help section.
I hope the issue is now a little clearer for everyone.

• Target String: Reference to the current string on the translation server:
  https://localize.drupal.org/translate/languages/de/translate?sid=286
• Benefit: This allows translators to use specific terms like "Canvas-Seiten" instead of a generic term that conflicts with the main Content menu.

Proposed resolution

If we decide to actually do this:

• Add a translation context to the menu link (add title_context to canvas.links.menu
• Add a translation context to the Page entity type definition: label, label_collection, label_singular, label_plural....
• Grep for other usages of t() and TranslatableMarkup where this might be relevant too.

User interface changes

The English UI remains "Pages". For all other languages, site administrators and translators gain the ability to translate the Canvas navigation link independently from the standard Content "Pages" link.