minor #15293 [Validator] Make it clear that configuring a constraint doesn't enforce anything (rpkamp)

This PR was merged into the 4.4 branch.

Discussion
----------

[Validator] Make it clear that configuring a constraint doesn't enforce anything

<!--

If your pull request fixes a BUG, use the oldest maintained branch that contains
the bug (see https://symfony.com/releases 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 `5.x` for features of unreleased versions).

-->

This is (probably) trivial for people who've been working for Symfony for a longer time, but I found myself needing to explain this on more than one occasion, so I think it would be good to mention it.

Commits
-------

16050c8 Make it clear that configuring a constraint doesn't enforce anything

Author: javiereguiluz

validation.rst

@@ -47,7 +47,7 @@ order to be valid. These rules are usually defined using PHP code or
 annotations but they can also be defined as ``.yaml`` or ``.xml`` files inside
 the ``config/validator/`` directory:
 
-For example, to guarantee that the ``$name`` property is not empty, add the
+For example, to indicate that the ``$name`` property must not be empty, add the
 following:
 
 .. configuration-block::
@@ -110,6 +110,11 @@ following:
             }
         }
 
+Adding this configuration by itself does not yet guarantee that the value will
+not be blank; you can still set it to a blank value if you want.
+To actually guarantee that the value adheres to the constraint, the object must
+be passed to the Validator Service to be checked.
+
 .. tip::
 
     Symfony's validator uses PHP reflection, as well as *"getter"* methods, to