minor symfony#18756 Remove paragraph about the impossibility to typehint a property (l-vo)

This PR was merged into the 5.4 branch.

Discussion
----------

Remove paragraph about the impossibility to typehint a property

<!--

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 `6.x` for features of unreleased versions).

-->

Commits
-------

974914f Remove paragraph about the impossibility to typehint a property

Author: OskarStark

service_container/injection_types.rst

@@ -364,15 +364,11 @@ Another possibility is setting public fields of the class directly::
         };
 
 There are mainly only disadvantages to using property injection, it is similar
-to setter injection but with these additional important problems:
+to setter injection but with this additional important problem:
 
 * You cannot control when the dependency is set at all, it can be changed
   at any point in the object's lifetime.
 
-* You cannot use type hinting so you cannot be sure what dependency is injected
-  except by writing into the class code to explicitly test the class instance
-  before using it.
-
 But, it is useful to know that this can be done with the service container,
 especially if you are working with code that is out of your control, such
 as in a third party library, which uses public properties for its dependencies.