GH-40727: [C++][Gandiva] 'ilike' function does not work

[lriggs]

Rationale for this change

Bug fix for GH-40727

What changes are included in this PR?

Register the 'ilike' function.
Added unit test.

Are these changes tested?

Yes, unit test.

Are there any user-facing changes?

No.

• GitHub Issue: [Gandiva] 'ilike' function does not work #40727

[github-actions]

⚠️ GitHub issue #40727 has been automatically assigned in GitHub to PR creator.

[lidavidm]

Can you rebase again? This has picked up unrelated changes

[lriggs]

Can you rebase again? This has picked up unrelated changes

Trying to, not sure how these got in there.

[kou]

+1

[conbench-apache-arrow]

After merging your PR, Conbench analyzed the 7 benchmarking runs that have been run so far on merge-commit d96fc69.

There were 2 benchmark results with an error:

• Commit Run on ursa-i9-9960x at 2024-03-22 22:27:11Z
  • file-read (Python) with compression=snappy, dataset=fanniemae_2016Q4, file_type=parquet, output_type=dataframe
  • file-read (Python) with compression=snappy, dataset=fanniemae_2016Q4, file_type=parquet, output_type=dataframe

There were 3 benchmark results indicating a performance regression:

• Commit Run on ursa-i9-9960x at 2024-03-22 22:27:11Z
  • tpch (R) with engine=arrow, format=native, language=R, memory_map=False, query_id=TPCH-06, scale_factor=1
  • tpch (R) with engine=arrow, format=parquet, language=R, memory_map=False, query_id=TPCH-06, scale_factor=1
• and 1 more (see the report linked below)

The full Conbench report has more details. It also includes information about 6 possible false positives for unstable benchmarks that are known to sometimes produce them.