[Bug] source_table='your_source_table_name_here' must be all lower case

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the issue

the source_table_name parameter HAVE to be lower case. Using all uppercase as is copied from Snowflake will error out with sql syntax error line 1 'limit'

Encountered an error:
Runtime Error
Database Error in model stratavar_quote_line_fm (models/salesforce_critical/stratavar_quote_line_fm.sql)
001003 (42000): SQL compilation error:
syntax error line 1 at position 0 unexpected 'limit'.

setting using_quoted_identifier to true doesn't do anything.

### Relevant error log or model output

```shell
limit 500
/* {"app": "dbt", "dbt_version": "2026.5.6+6cb8948", "profile_name": "user", "target_name": "default", "node_id": "model.fivetran_formula_transformation.stratavar_quote_line_fm"} */
Snowflake adapter: Snowflake query id: 01c43c50-0a11-c4aa-0002-937e21120272
Snowflake adapter: Snowflake error: 001003 (42000): SQL compilation error:
syntax error line 1 at position 0 unexpected 'limit'.
Database Error in model stratavar_quote_line_fm (models/salesforce_critical/stratavar_quote_line_fm.sql)
001003 (42000): SQL compilation error:
syntax error line 1 at position 0 unexpected 'limit'.
```

### Expected behavior

i am not sure if this is an expected behavior, but this isn't documented anywhere. I found the solution through trial/error.

### Possible solution

_No response_

### dbt Project configurations

it is default, nothing touched.

### Package versions

packages:
- package: fivetran/salesforce_formula_utils
version: [">=0.11.0", "<0.12.0"] # we recommend using ranges to capture non-breaking changes automatically

### What database are you using dbt with?

snowflake

### How are you running this dbt package?

dbt Cloud™

### dbt Version

dbt cloud versionless

### Additional Context

_No response_

### Are you willing to open a PR to help address this issue?

- [ ] Yes.
- [ ] Yes, but I will need assistance.
- [ ] No.

Start with models/salesforce_critical/stratavar_quote_line_fm.sql and trace how the source_table_name parameter is handled by the package macros. Reproduce the failure with an uppercase Snowflake source table and compare it with the lower-case workaround. Done means uppercase source_table_name values work correctly, or the required casing is documented if that behavior is intentional.

Written by the indexing model from the issue text.