Fixed createView handling of replaceIfExists=true when the string "replace" exists in the view definition

[filipelautert]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

• Verifies if the "OR" statement exists within the sql (so we have "OR REPLACE" instead of just "REPLACE")
• Creates some tests.
• Fixes createView replaceIfExists doens't work if using replace function in view definition #1849

Things to be aware of

• None

Things to worry about

• None

Additional Context

• None

[github-actions]

Unit Test Results

  4 668 files  +12    4 668 suites  +12   36m 45s ⏱️ - 7m 4s
  4 631 tests +  3    4 416 ✔️ +  3     215 💤 ±0  0 ❌ ±0 
54 744 runs  +36  49 724 ✔️ +36  5 020 💤 ±0  0 ❌ ±0 

Results for commit a23e3d8. ± Comparison against base commit 031928b.

[XDelphiGrl]

PR fixes a bug where including the string "replace" in a SELECT statement for a view was improperly handled when createOrReplace=true.

• New unit tests added to validate createOrReplace=false and createOrReplace=true with the string "replace" in the SELECT statement.
• No additional testing required.

APPROVED