@W-14371508 fix: JS Substitute DB tests for parity

[ashwanikmr121]

Add missing DB tests for the Substitute function to bring it to parity with Postgres tests including the JS path

[ashwanikmr121]

@sahil-here As discussed, added tests to other DB files for parity purposes. However, I wanted to check If we expect the relevant gold files for other DBs to also be generated as there are none generated for me like it was generated for Postgres in the PR: #140.

Probably the gold files are not changed as the DB tests other than Postgres do not include an execution path for Javascript where the code changes have gone in.

[sahil-here]

s to other DB files for parity purposes. However, I wanted to check If we expect the relevant gold files for other DBs to also be generated as there are none generated for me like it was generated for Postgres in the PR: #140.

The goldfiles for other DBs will not change as the goldfiles only contain generated SQL for execution path sql. And you are right, the goldfile for Postgres changed, as it has an execution path javascript, which will generate the Javascript code in the goldfile which has changed based on the PR.

Also, if you want to run all tests for all DB substrates, you can use a command like: mvn -P db-tests test to run these db tests.