Add explanation about prefix decision

See #9886, I left out
reasons related to overhead during compilation steps because that might
be too technical.

Author: greg0ire

bundles/best_practices.rst

@@ -382,7 +382,11 @@ Services
 --------
 
 If the bundle defines services, they must be prefixed with the bundle alias.
-For example, AcmeBlogBundle services must be prefixed with ``acme_blog``.
+For example, AcmeBlogBundle services must be prefixed with ``acme_blog``
+instead of using fully qualified class names like in a project. This is
+because a bundle should not pollute the list of autowireable types with
+its own services, and do avoid service ids collisions with projects or
+other bundles that might do so.
 
 In addition, services not meant to be used by the application directly, should
 be :ref:`defined as private <container-private-services>`. For public services,