Issue 7290: removed duplicate tableProperties instance

[TheOnlyOrchid]

Issue

• My PR fully resolves issue Remove extra TableProperties from AggregationFilteringIteratorTest #7290 by removing the duplicate tableProperties instance.
  • Resolves Remove extra TableProperties from AggregationFilteringIteratorTest #7290

Tests

• My PR does not add any tests, as it is a small PR to edit a singular test

Documentation

• My PR does not add any documentation, as it is a small change that, in my opinion, does not need any documentation.
  • If anyone disagrees with this assertion, I am happy to review and add any necessary documentation.

[patchwork01]

Thanks very much for the help. Now that there's only one TableProperties field we don't need it to be a parameter for the helper methods any more. Do you want to update applyIterator and createIterator as part of this PR, or should we make that a separate issue?

[TheOnlyOrchid]

I would be happy to have a look at that later today! I will hopefully have a pull request posted
by tomorrow

[TheOnlyOrchid]

I added another commit that changes the function signature of applyIterator and createIterator to remove the redundant parameters.

I also noticed that with the new changes, it may be worth changing the function names, so it is easier to interpret its behaviour.

Previously you could infer the intent was to create an iterator for the tableProperties field, as the function call would include "tableProperties". However the function signature change now obscures this behaviour, requiring manual inspection of the function to interpret the behaviour.

Unfortunately I am now unavailable for the next two weeks, so to streamline the process I did not include this change, as it may require further input from me.

[patchwork01]

I see what you mean. I'd be happy with that, or if you preferred to leave applyIterator and createIterator as they were. I think we can go ahead with what we've got, thanks.