[BUG] Exposures with names set dynamically by variables get incorrectly "fixed"

[QMalcolm]

People can dynamically set the name of an exposure by doing something like the following:

# my_exposure.yaml
exposures:
  - name: "{{ env_var('DBT_ENV_EXPOSURE_NAME_PREFIX') }}_my_exposure"
     ...

In dbt-core, we don't issue a ExposureNameDeprecation deprecation for this because we resolve the env var, and then validate that the resolved templated name is valid. However, in dbt-autofix we don't resolve the env var, view the name as having invalid characters, and attempt to "fix" it. In the above example exposure, autofix will "fix" the name to be _env_varDBT_ENV_EXPOSURE_NAME_PREFIX__my_exposure 😬

[chayac]

Hmmm interesting - we do have some logic to ignore configs with Jinja because we aren't expanding them, but I guess we aren't applying that to this changeset. I added a unit test to debug and confirmed that this was also an issue in earlier versions - we reworked the Jinja parser recently so I wanted to make sure it wasn't related to that. I'll use that for some further debugging but probably not immediately :)