Consider adding `element` filter to base `HTML` interactor

Unlike business app authors, component library authors often need to make assertions on the actual layout a component and how it renders. One way to deal with this is to add custom filters, like clientTop if you need to make an assertion on what the coordinates of the top, you can add a filter.

await component.has(clientTop: 10);

But a filter that nobody should ever use except in the context of the component library itself is of dubious value.

One option is to make element a filter, that way, you can implement custom matchers on it to your heart's content. So instead of having a clientTop filter, you can just have a matcher:

await component.has(element: withClientTop(10));

Start with the base HTML interactor and review how filters and custom matchers are represented. Compare the proposed element filter with the clientTop example, then define what behavior and tests would demonstrate that component authors can apply custom matchers to the underlying element.