minor #12236 [Translator] Recommending real message id for shared bundles (yceruto)

This PR was merged into the 3.4 branch.

Discussion
----------

[Translator] Recommending real message id for shared bundles

Using the "keyword" method to create translation message in public/shared bundles is painful sometimes, because apps with single-lenguage MUST activate the `translator` layer to see the final message, so worse performance.

DX-wise, the "keyword" method is "practical" (nowaday smart IDEs can replace texts easier), but when we're creating a bundle we should also think that "translation" is optional for apps.

Commits
-------

0def709 Recommending real message id for shared bundles

Author: javiereguiluz

components/translation/usage.rst

@@ -164,7 +164,10 @@ recommended format. These files are parsed by one of the loader classes.
     read "Symfony is really great" in the default locale.
 
     The choice of which method to use is entirely up to you, but the "keyword"
-    format is often recommended.
+    format is often recommended for multi-language applications, whereas for
+    shared bundles that contain translation resources we recommend the real
+    message, so you application can choose to disable the translator layer
+    and you will see a readable message.
 
     Additionally, the ``php`` and ``yaml`` file formats support nested ids to
     avoid repeating yourself if you use keywords instead of real text for your