[Bug] Use consistent secret scrubbing

[emmyoop]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

When secrets are used in the jinja log function, they do not get scrubbed to ***** as they do elsewhere in logs. They appear in the log as the literal text we use to ensure they are not leaked.

To be clear, the secrets are not currently leaked but the behavior is inconsistent with how secrets appear elsewhere in logs.

Expected Behavior

Secrets should display as ***** in logs.

Steps To Reproduce

1. Define a packages.yml

packages:
    - local: "{{ log(env_var('DBT_ENV_SECRET_MINE'), info = true) }}"  

2. Run DBT_ENV_SECRET_MINE=abc dbt deps
3. See in the log

$$$DBT_SECRET_START$$$DBT_ENV_SECRET_MINE$$$DBT_SECRET_END$$$

Relevant log output

No response

Environment

- OS:
- Python:
- dbt:

Which database adapter are you using with dbt?

No response

Additional Context

No response