Discover and Define M25-05 reporting requirements

## User Story

In order to support agencies reporting requirements from M25-05, agency metadata stewards want data.gov to provide all possible reporting requirements related to M25-05.

## Acceptance Criteria

- [ ] GIVEN the metrics page exists https://data.gov/metrics/ \
WHEN a review of M25-05 reporting requirements is complete \
THEN a list of available metrics from data.gov GA4 that matches the M25-05 requirements is available.

## Background

[Any helpful contextual notes or links to artifacts/evidence, if needed]

## Security Considerations ([required](https://nvd.nist.gov/800-53/Rev4/control/CM-4))

[comment]: # "Our SSP says 'The Data.gov team ensures security implications are considered as part of the agile requirements refinement process by including a section in the issue template used as a basis for new work.' so please don't remove this section without care."
None

## Sketch

Review M25-05 requirements for reporting. Look for anything that can be captured by data.gov. Make sure to give caveats on the incompleteness. For example, datasets all direct to direct file downloads, API's, or other data access points. Once these are found in data.gov, a user can use them directly (or may have found them from another source such as an agency website). So any metrics built on data.gov's tracking of direct downloads is inherently incomplete.

However, given that some agencies do not have the ability to track their own downloads, this might be a helpful replacement or cover.