We need to update project archival features to respect group-level archival state by migrating from project-only archival checks to ancestor-aware methods and scopes. ### Context With the introduction of [group archival](https://gitlab.com/groups/gitlab-org/-/epics/15019), projects are now implicitly archived when their parent group is archived. The current implementation sets `namespace.namespace_settings.archived = true` on the group without cascading this attribute to child projects/subgroups. This design choice was made for performance reasons, as cascading the archival state to all descendants would require processing potentially thousands of records, and doing so in a background worker would lead to poor UX with delayed archival effects. Instead, the archival state is determined dynamically by checking ancestor namespaces through new methods and scopes. ### Problem Many project archival features still rely on the legacy `project.archived` attribute and related scopes ([archived](https://gitlab.com/gitlab-org/gitlab/-/blob/d6519886f59145994e8a1299ca1250035b5f4981/app/models/project.rb#L829)/[non_archived](https://gitlab.com/gitlab-org/gitlab/-/blob/d6519886f59145994e8a1299ca1250035b5f4981/app/models/project.rb#L836)), which only check the project's own archival state. This causes these features to ignore group archival, leading to inconsistent behavior where archived groups' projects are not properly treated as archived. ### Goal Ensure all project archival features respect both project-level AND group-level archival by: 1. **Migrating method calls:** - Replace `project.archived` -> [`project.self_or_ancestors_archived?`](https://gitlab.com/gitlab-org/gitlab/-/blob/e80aae9cb2ff62f56c6b8244cf657f71049c2326/app/models/project.rb#L3021) 2. **Migrating scopes:** - Replace [`archived`](https://gitlab.com/gitlab-org/gitlab/-/blob/d6519886f59145994e8a1299ca1250035b5f4981/app/models/project.rb#L829) scope -> [`self_or_ancestors_archived`](https://gitlab.com/gitlab-org/gitlab/-/blob/e80aae9cb2ff62f56c6b8244cf657f71049c2326/app/models/project.rb#L830) scope - Replace [`non_archived`](https://gitlab.com/gitlab-org/gitlab/-/blob/d6519886f59145994e8a1299ca1250035b5f4981/app/models/project.rb#L836) scope -> [`self_and_ancestors_non_archived`](https://gitlab.com/gitlab-org/gitlab/-/blob/e80aae9cb2ff62f56c6b8244cf657f71049c2326/app/models/project.rb#L837) scope 3. **Building additional services/workers where needed:** - Some features may require new services or workers to handle group archival properly. Some of these are tracked in https://gitlab.com/groups/gitlab-org/-/epics/19492+. ### Implementation Approach The issues under this epic contain search results for the "archived" keyword in the codebase, with one issue per team containing the relevant occurrences for that team's domain. Each team should review its issue and update the affected code to use the new ancestor-aware methods and scopes or create new services/workers wherever applicable.