Exclude environment variables when generating package lockfile

[ttusing]

Resolves #11953

Problem

When using environment variables in git package URLs, dbt deps generates different package hashes on different machines even when the actual package specification is identical. This causes several problematic behaviors:

Solution

Added a new optional exclude-env-vars-from-hash field to git packages that allows excluding environment variables from hash calculation while still using them for actual git operations.

GitPackage field with YAML alias support
to_dict_for_hash() method: Returns dictionary using unrendered values when flag is set
[_create_sha1_hash()]: Modified to use new method when available, falls back to existing behavior
Backward compatible: Existing packages continue to work unchanged (flag defaults to false)

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 or 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.
• This PR includes type annotations for new and modified functions.

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Tobie Tusing.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Tobie Tusing.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

[dbeatty10]

@ttusing this file is empty -- was there intended to be content in here?

[ttusing]

fixed - also fixed my commit history for the CLA bot I think, though it looks like I need to sign those commits. will address that along with any feedback!

[cla-bot]

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Tobie Tusing.
This is most likely caused by a git client misconfiguration; please make sure to:

1. check if your git client is configured with an email to sign commits git config --list | grep email
2. If not, set it up using git config --global user.email [email protected]
3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails