Add 'strictMatching' property to InjectLink annotation to allow lenient strategy

Although it is now possible to avoid to define all bindings and get data from the uri, it fails if the query parameters are defined in the Resource but are not available in the uri, which often happens since query parameters are most of the time optional.
Unfortunately, the code in ELLinkBuilder doesn't allow simply to separate path and query parameters in the template.
We then propose to add a 'strictMatching' flag to deactivate the PropertyNotFoundException that is typically thrown, and instead allow to pass a null value to the uriBuilder.
By default, strictMatching is true to keep compatibility with current behavior
#### Affected Versions
[2.22]

Start by reading the InjectLink annotation and ELLinkBuilder, then trace where PropertyNotFoundException is raised while building URIs. Done means adding a strictMatching option that defaults to true while allowing missing query parameters to produce null values in lenient mode; verify the existing strict behavior remains compatible.

Written by the indexing model from the issue text.