Unnecessary walking even if action filter is set

[alexanderkirtzel]

Describe the bug
Data properties and nested entities are captured for entities that don't match the filter. This could result in performance issues.

Expected behavior
If an action filter is set data-elbaction="click(foo)" only the foo entity should be processed by the walker-algorithm, not any possible bar entity for example.