Update is_dyanmic check for new accpetable value after snowflake bundle change 2024_03

[McKnight-42]

resolves #1016
docs dbt-labs/docs.getdbt.com/#

Problem

https://docs.snowflake.com/en/release-notes/bcr-bundles/2024_03_bundle updates the is_dynamic field from YES to Y which we query to see if a table is a dynamic table for not.

this currently fails due to looking for different values from when the is_dynamic field was first introduced via #937

Solution

updating to check for both values for users pre and post change and updating same similar call in test

ISSUE:
we had to rebase this branch due to local repo getting corrupted leading to excessive amounts of extra commits that didn't mean or point to anything.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-snowflake contributing guide.

[mikealfare]

This looks right. Any idea why there are 67 commits on this PR, dating back to last year though?

[VersusFacit]

This PR is going to need to be rebased or something since it's way off main.

[McKnight-42]

Closing as currently thoughts are that the real issue is around changes to show terse kind options for the bundle in question.