Show the caching period in the repository sidebar

What does this MR do and why?

A remote repository revalidates cached artifacts and cached metadata on two windows Artifact Registry stores. Neither window had a place on the repository detail page, so a viewer had to open the edit form to see them. The sidebar now names both under a Caching period heading.

Both repository reads bind to the schema for this. The detail read and the edit prefill answered several fields from the local mock resolvers, and the schema carries all of them now, so both ask the server instead:

• get_repository_detail.query.graphql drops @client from artifactsCount, createdAt, createdBy, updatedBy, and settings, and selects the two caching windows the sidebar renders.
• get_repository.query.graphql drops @client too. It selected localRemoteSettings, a field only typedefs.graphql declared; the schema names the same field settings, so binding the read renames it rather than leaving a local alias beside the schema's own field. typedefs.graphql loses the local field and its type.
• The local update mutation still resolves its whole payload locally, so the settings mock resolver stays until that mutation binds as well.

A container remote caches no metadata, so that line is dropped rather than reported as zero. Each sidebar section sets its own gap now, and the root wrapper drops gl-text-sm, so the sections space their lines the same way at the default body size.

All three documents were validated against the schema dump plus typedefs.graphql. ee/spec/frontend/fixtures/artifact_registry/repository.rb expects the five newly server-backed fields, so the detail spec keeps rendering the schema's own answer instead of hand-written stand-ins.

No changelog trailer: the UI sits behind artifact_registry_ui, which is default_enabled: false.

References

• Feature: gitlab-org#22453
• Part of Step 14 of Repository detail plan
• Feature flag rollout: #605113

Screenshots or screen recordings

Before	After

How to set up and validate locally

1. In the Rails console, enable the flag:

   Feature.enable(:artifact_registry_ui)

2. Visit an organization's Artifact Registry repositories at /o/<organization>/-/artifact_registry/<slug>/repositories.

3. Open a remote repository. The sidebar names the artifact window, and the metadata window as well for any format other than Docker or OCI.

4. Open a hosted repository. No Caching period section renders, because a hosted repository caches nothing.

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.