User attributes in SQL are not compatible with persisted NDTs (and aggregate awareness)

[DylanBaker]

This isn't so much a bug with Spectacles as it is an issue with Looker that we want to track.

Often, in order to test Looker with changes to code in tools like dbt, Spectacles users use user attributes in sql_table_name and derived_table fields in order to programatically alter which dataset in the warehouse gets used.

Unfortunately, when aggregate awareness is being used, and therefore persisted NDTs are in place, users get an error that says the persistent NDTs can't reference user attributes.

Annoyingly, typically only the Spectacles user in Looker will be the one who leverages the user attributes, so it otherwise is as good as hard-coded for the non-Spectacles users. Nevertheless, it seems like this would be a blocker for dbt <> Spectacles testing.