chore(ci): bump SHAs in _local workflows

[jdalton]

Summary

Layer 4 cascade: updates _local-not-for-reuse-ci.yml, _local-not-for-reuse-provenance.yml, and _local-not-for-reuse-weekly-update.yml to reference Layer 3 with inline zizmor security audit.

Cascade

• Layer 1: checkout action (feat(ci): add zizmor security audit to checkout action #184) ✓
• Layer 2b: setup-and-install (chore(ci): bump checkout SHA in setup-and-install #185) ✓
• Layer 3: ci.yml, provenance.yml (chore(ci): bump setup-and-install SHA in ci.yml and provenance.yml #186) ✓
• Layer 4: _local workflows ← this PR
• All consuming repos use the Layer 3 SHA (4ea01311d2612815dd255368fa757cfc527670f6)

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.