[BREAKING(functions)] Update post-deploy function logic to stop aggressively deleting conatiners

[taeold]

Today, CLI attempts to clean up GCF artifacts (container images) in Artifact Registry post function deploys.

Historically, this post-deploy cleanup task had not been too reliable, and the resulting warning logs have confused developers.

We are trying a different approach - instead of trying to clean up the artifacts on every deploy, we'll make it easy for developers to set up a Artifact Registry Cleanup Policy on repository used by Cloud Run functions.

Cleanup policies are a managed service feature that automatically removes container images based on configurable rules, providing a more robust and transparent solution.

As suggested in this change, we'll automatically set up a clean up policy post-function deployment if we detect that a clean up policy doesn't exist yet.

We'll soon be updating the documentations to clarify what developers should do in order to avoid small monthly cost for Firebase Function's use of Artifact Registry.

Fixes #4954, #4954, #8164, #4757

[chalosalvador]

@taeold I opened the PR #8318 which may be related to this PR. It updates the packagePath method to handle the correct names for the artifacts in GCF v1 and v2 (#8164)

[taeold]

@chalosalvador that's a good change, but I think I'm going to suggest that Functions still move on from trying to maintain the container cleanup logic. The logic is still used in functions:deletegcfartifacts command which users can use to manually purge their Artifact Repository repo if needed, so the PR is definitely helpful.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 62.79070% with 32 lines in your changes missing coverage. Please review.

Project coverage is 51.07%. Comparing base (7a7f3a5) to head (4df904f).
Report is 4 commits behind head on master.

Files with missing lines	Patch %	Lines
src/deploy/functions/release/index.ts	10.00%	18 Missing ⚠️
src/deploy/functions/prompts.ts	14.28%	12 Missing ⚠️
src/functions/artifacts.ts	96.15%	1 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8324      +/-   ##
==========================================
+ Coverage   50.94%   51.07%   +0.12%     
==========================================
  Files         425      425              
  Lines       30230    30362     +132     
  Branches     6192     6219      +27     
==========================================
+ Hits        15401    15507     +106     
- Misses      13446    13467      +21     
- Partials     1383     1388       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[inlined]

I like the compromise to the internal discussion that the deployment will succeed but we'll exit with non-zero if the there is no policy, no opt-out, is non-interactive, and force isn't set.