Remove private_key_path from _conection_keys

[McKnight-42]

resolves #949
docs dbt-labs/docs.getdbt.com/#

Problem

the field private_key_path could have a argument to be a qausi secret level like field that possibly should be removed from debug and being called in jinja

Solution

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the dbt-snowflake contributing guide.

[will-sargent-dbtlabs]

Hi Team! If we are able to get this reviewed and implemented, I believe this issue is a blocking issue (or contributing) for several major customers from using parse caching for jobs, so high-value win potential. Thanks @McKnight-42 for getting this edit in the pipeline!

[will-sargent-dbtlabs]

@McKnight-42 How long before this will be reflected in mt via dbt debug for versionless?

[McKnight-42]

@will-sargent-dbtlabs I don't have a exact timeframe I think we are doing some releases tomorrow, so we will create the bundles and stuff then and usually takes a few days or so to populate throughout cloud once its all out so sometime mid next week possibly? similar timeframe for 1.7 and 1.6 adapters once the backports are merged