Enable getRowFilter to be column aware

[huw0]

Description

Summary

Enable getRowFilter to be column aware.

Detail

Presently the access control interfaces provide getRowFilter with the security context, catalog name and schema name.

This works well when adding the row filter based on a restricted list of rules (FileBasedAccessControl) or where the metadata is known elsewhere (OPA or Ranger).

However this does not allow for filters to be dynamically added based on the columns.

For example - whenever a table has a security_group column, add a filter to enable row-level security against the user's current groups.

To enable this use case, this PR modifies the getRowFilter so that the List<ColumnSchema> is also passed in as a parameter, matching getColumnMasks.

Implementation Notes

• Backwards Compatibility - everything in trino-main calls the new method. However the old method is deprecated but called by the default implementation of the new method within the interfaces. Hopefully this preserves backwards compatibility?
• Testing - where is best to add coverage of this functionality?
• FileBasedAccessControl - I propose a follow on PR to make use of this functionality within FileBasedAccessControl and associated documentation.

Additional context and related issues

#1480 - original implementation of row filtering
#21046 - a question around this functionality

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

## SPI
* Enable row filtering to be column aware ({issue}`issuenumber`)