Add argument-less builder methods for boolean values

[kasiafi]

The TableArgumentSpecification builder is part of SPI for declaring
Table Functions. It assumes default values for boolean table argument
properties, and allows to change them using argument-less methods.
It is meant to provide the easiest and most intuitive way of declaring
Table Functions.

This is a SPI change.

No documentation needed.

[kasiafi]

@findepi how do I deal with SPI backwards compatibility assertions?

but could not find the following element(s):
2022-05-19T11:14:04.2842320Z  <["Method: public io.trino.spi.ptf.TableArgumentSpecification$Builder io.trino.spi.ptf.TableArgumentSpecification$Builder.rowSemantics(boolean)",
2022-05-19T11:14:04.2842672Z     "Method: public io.trino.spi.ptf.TableArgumentSpecification$Builder io.trino.spi.ptf.TableArgumentSpecification$Builder.pruneWhenEmpty(boolean)",
2022-05-19T11:14:04.2843027Z     "Method: public io.trino.spi.ptf.TableArgumentSpecification$Builder io.trino.spi.ptf.TableArgumentSpecification$Builder.passThroughColumns(boolean)"]>

Should I deprecate the old methods instead of remove? I'd rather remove them right away, since this is a new feature with no usage so far.

[findepi]

Should I deprecate the old methods instead of remove?

i think so

I'd rather remove them right away, since this is a new feature with no usage so far.

You'd need to add exclusion to io.trino.spi.TestSpiBackwardCompatibility#BACKWARD_INCOMPATIBLE_CHANGES

[findepi]

i'm fine either way

[martint]

Should I deprecate the old methods instead of remove? I'd rather remove them right away, since this is a new feature with no usage so far.

The feature is experimental and it’s not being used by anyone, so no point in trying to keep it compatible. Let’s just remove it.

I expect we’ll have to make a few more changes as we continue implementing the rest of the functionality to be able to execute the functions.

[kasiafi]

@findepi I removed the old methods and added exclusion. Is it ready to go?