[native] Add test for substring alias

[yabinma]

== NO RELEASE NOTE ==

[aditi-pandit]

Thanks @yabinma

[aditi-pandit]

@yabinma : Please fix the failing tests... Think that is because presto-teradata-functions module is not registered on the Java side. Please can you check.

[yabinma]

@yabinma : Please fix the failing tests... Think that is because presto-teradata-functions module is not registered on the Java side. Please can you check.

Got a chance to check today. substring is already registered in presto-teradata-functions,

presto/presto-teradata-functions/src/main/java/com/facebook/presto/teradata/functions/TeradataStringFunctions.java

Line 88 in d9f71c4

public static Slice substring(

I was thinking it might be missed in common place, that's why I added another substring registration in com.facebook.presto.operator.scalar.StringFunctions
But. the workflow failed with error message,

25/05/30 06:03:17 WARN PluginManagerUtil: No service providers of type com.facebook.presto.spi.RouterPlugin
25/05/30 06:03:17 WARN PluginManagerUtil: No service providers of type com.facebook.presto.spi.CoordinatorPlugin
25/05/30 06:03:17 INFO PluginManagerUtil: Installing com.facebook.presto.teradata.functions.TeradataFunctionsPlugin
25/05/30 06:03:17 INFO PluginManager: Registering functions from com.facebook.presto.teradata.functions.TeradataDateFunctions
25/05/30 06:03:17 INFO PluginManager: Registering functions from com.facebook.presto.teradata.functions.TeradataStringFunctions
java.lang.RuntimeException: java.lang.IllegalArgumentException: Function already registered: presto.default.substring(varchar(x),bigint,bigint):varchar(x)

So the previous "substring is not registered" error might not be caused by function register code. I will check the workflow later how the test server is configured. It might need to add the TeradataStringFunctions registration in the configuration.

[yabinma]

I rollback the code to contain the test case changes only and the workflow returned the same error message that "substring is not registered"

It failed in step: prestocpp-linux-presto-e2e-tests: then I checked the workflow code in https://github.com/prestodb/presto/blob/fda51140321fca27f8054786c3ceedd555700cb5/.github/workflows/prestocpp-linux-build-and-unit-test.yml#L93C3-L93C36

The dependency image shown: container:
image: prestodb/presto-native-dependency:0.293-20250522140509-484b00e

My Velox PR was merged in 20250523. This might be one of the reasons.

@aditi-pandit , do you know how frequently the test image is updated?