minor #10956 Explicitly list _field-name_entry_parts (welcoMattic)

This PR was merged into the 4.2 branch.

Discussion
----------

Explicitly list _field-name_entry_parts

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/roadmap for the list of maintained branches).

If your pull request documents a NEW FEATURE, use the same Symfony branch where
the feature was introduced (and `master` for features of unreleased versions).

-->

Commits
-------

ea25ab7 Explicitly list _field-name_entry_parts

Author: javiereguiluz

form/form_themes.rst

@@ -283,7 +283,7 @@ Fragment Naming for Collections
 When using a :doc:`collection of forms </form/form_collections>`, the fragment
 of each collection item follows the pattern ``_field-name_entry_part``. For
 example, if your form field is named ``tasks``, the fragment for each task will
-be named ``_tasks_entry`` (``_tasks_entry_label``, ``_tasks_entry_label``, etc.)
+be named ``_tasks_entry`` (``_tasks_entry_row``, ``_tasks_entry_label``, ``_tasks_entry_widget``, ``_tasks_entry_error``)
 
 Template Fragment Inheritance
 .............................