SNOW-2443512: Add support for scalar string and binary functions ( part 2 )

[sfc-gh-aherreraaguilar]

1. Which Jira issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-2443512

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
     • If this test skips Local Testing mode, I'm requesting review from @snowflakedb/local-testing
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency
   • If this is a new feature/behavior, I'm adding the Local Testing parity changes.
   • I acknowledge that I have ensured my changes to be thread-safe. Follow the link for more information: Thread-safe Developer Guidelines
   • If adding any arguments to public Snowpark APIs or creating new public Snowpark APIs, I acknowledge that I have ensured my changes include AST support. Follow the link for more information: AST Support Guidelines

3. Please describe how your code solves the related issue.

Add support for the scalar string and binary functions:

• hex_decode_string
• jarowinkler_similarity
• parse_url
• regexp_instr
• regexp_like
• regexp_substr
• regexp_substr_all
• rtrimmed_length
• space
• split_part

[sfc-gh-mvegaalvarez]

lgtm

[sfc-gh-aling]

I have two questions here:

1. do we need to check the dependency between the optional args? what happen if occurrence is set but position is not set. I feel this is not allowed in sql as in sql the arguments are positional, users have to specify position first then occurrence then possibly the rest.

2. I see there is a long note about
   Note By default, REGEXP_INSTR returns the begin or end character offset for the entire matching part of the subject. However, if the e (for “extract”) parameter is specified, REGEXP_INSTR returns the begin or end character offset for the part of the subject that matches the first sub-expression in the pattern. If e is specified but a group_num is not also specified, then the group_num defaults to 1 (the first group). If there is no sub-expression in the pattern, REGEXP_INSTR behaves as if e was not set. For examples that use e, see [Examples](https://docs.snowflake.com/en/sql-reference/functions/regexp_instr#examples) in this topic.

shall we not set the default value from client at all and let server decide the default rule? I feel this way it's simpler

[sfc-gh-aherreraaguilar]

Hello @sfc-gh-aling ,
regarding these questions, the reason why I am setting the default values is that when I call the function
builtin("regexp_instr", _emit_ast=_emit_ast)(*args)
, passing the *args list, it does not explicitly indicate the name for each parameter. So, for example, if I send regexp_instr(A,B,C) the order will be the same when calling the builtin, but when calling something like regexp_instr(A, C=C), the call in the builtin will be regexp_instr(A, C)

[sfc-gh-aling]

same comment as above

[sfc-gh-aling]

same for this func

[sfc-gh-aherreraaguilar]

@sfc-gh-mvegaalvarez @sfc-gh-aling , I tried to reopen this PR, but it is not possible, so I created this new PR to merge these changes.