Update apply_regex.sql

[dprovder]

fix for runtime error when running hcc_suspecting__int_prep_egfr_labs using duckDB

Describe your changes

added apply_regex implementation for duckDB to fix

Runtime Error in model hcc_suspecting__int_prep_egfr_labs (models/hcc_suspecting/intermediate/hcc_suspecting__int_prep_egfr_labs.sql)
  Catalog Error: Scalar Function with name regexp_like does not exist!
  Did you mean "regexp_replace"?
  LINE 79:     where regexp_like(result, '^[+-]?([0-9]*[.])?[0-9]+$')

How has this been tested?

running dbt build with a profile that uses the dbt-duckDB adapter:

• Tuva project package version (e.g. 0.6.0): 0.9.0
• dbt version (e.g. 1.7): 1.8.3
• dbt type (e.g. dbt cloud or dbt CLI): dbt core
• Data warehouse (e.g. Snowflake): DuckDB

locally tested & So did @sarah-tuva

Checklist before requesting a review

• [ ] I have added at least one Github label to this PR (bug, enhancement, breaking change,...)
• [ ] My code follows style guidelines
• [ ] (New models) YAML files are categorized by sub folder and models listed in alphabetical order
• [ ] (New models) I have added a config to each new model to enable it for claims and/or clinical data
• [ ] (New models) I have added the variable tuva_last_run to the final output
• [ ] (Optional) I have recorded a Loom to explain this PR

Package release checklist

• [ ] I have updated dbt docs
• [ ] I have updated the version number in the dbt_project.yml

(Optional) Gif of how this PR makes you feel

Loom link

[sarah-tuva]

Resolves #536 and previously tested locally by @eldon-tuva.

[sarah-tuva]

[github-actions[bot]]

Workflow has finished with the following statuses:

• Snowflake: cancelled

• Snowflake: cancelled

• Snowflake: cancelled

• Redshift: cancelled

• Redshift: cancelled

• Redshift: cancelled

• BigQuery: cancelled

• BigQuery: cancelled

• BigQuery: cancelled