Add a warning when regenerating the lockfile for packages and there is a hash mismatch

[ttusing]

Resolves #11913

Problem

Sometimes, the lockfile is regenerated and this is not very visible to the user. This can cause package updates at unexpected times, leading to instability.

Solution

Add a warning when the lockfile is regenerated

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

[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 contributing guide.

[ttusing]

🤔 did the CLA check fail because I didn't sign the commit with my email address? Think so.

Can fix that once thats confirmed/PR is reviewed for being desirable change and also add the changie