DRAFT: Resolve "Support fetching last successful from Artifacts Archive with API"

What does this MR do and why?

This change adds a new feature to improve how GitLab finds and downloads job artifacts (files created by CI/CD jobs).

Previously, when someone requested artifacts from a specific job, GitLab would only look in the most recent successful pipeline. If that job didn't exist in the latest pipeline, it would return an error.

Now, users can optionally search across all successful pipelines to find the job they need. This is helpful when pipeline configurations change and certain jobs don't run in every pipeline.

To make this efficient, the system implements a smart caching mechanism that remembers successful builds for quick retrieval later. When a build completes successfully and has artifacts, it gets cached for one hour. When someone searches for artifacts, the system first checks the cache for a quick response. If not found in cache, it searches through up to 100 recent successful pipelines and then caches any found results for future requests.

The feature is opt-in through a new API parameter called search_all_successful_pipelines. This maintains backward compatibility while providing the enhanced search capability when needed. The documentation has been updated to explain how to use this new feature and its performance characteristics.

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #515864