[CT-3451] Move application logic in common.utils.jinja to common.clients.jinja

[MichelleArk]

Housekeeping

• I am a maintainer of dbt-core

Short description

As part of the adapters decoupling work, much of dbt/clients/jinja and dbt/utils/jinja have moved to dbt/common. As highlighted by @colin-rogers-dbt in dbt-labs/dbt-core#9149 (comment), it'd be worth determining whether certain 'utils' are defining application logic and should themselves move to dbt.common.clients.jinja

Acceptance criteria

A spike report that highlights any potential approaches and their tradeoffs, as well as a summary of any potential blockers encountered.

Impact to Other Teams

N/A - should be a refactor.

Will backports be required?

nope

Context

dbt-labs/dbt-core#9149

[github-actions]

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

[github-actions]

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.