enhance error reporting for unrecognized table features

[sebastiantia]

Please describe why this is necessary.

Currently, the protocol parser fails on the first unrecognized table feature it encounters. This behavior means that if a protocol contains multiple unrecognized features (for example, newerDeltaFeature1 and newerDeltaFeature2), only one error is reported and the user remains unaware of the others. This issue proposes to modify the implementation so that parsing continues to collect all unrecognized features and then reports them collectively in a single error message.

Describe the functionality you are proposing.

There exists the UnrecognizedReaderFeature(String) and UnrecognizedWriterFeature(String) features which are currently only used in tests to act as unsupported table features.

Leverage these features to collect all unrecognized table features during protocol parsing and then report them in a single error message, for example:
ERROR: Found unsupported reader features: newerDeltaFeature1, newerDeltaFeature2

Make sure to update current tests:
test_roundtrip_writer_features & test_roundtrip_reader_features

Additional context

No response