Improve default value filter to work on non-existing list items

Coming from #2654892: Allow using data filters in placeholder tokens → :

The default value currently only works if no "missing data" exception is thrown, but this happens if you want to do node:field_multiple:4|default('some') for a not existing field value. So we should catch those exceptions and pass on NULL to filters allowing NULL input.

For that to work, we'll also need the possibility to apply the property path on definitions only. That way we can catch the missing data exception of e.g. node:field_multi:3:value because the 4th item is not set, but then fetch the definition of node:field_multi:3:value and pass it on to the default filter. That way, the filter knows the target data type.