document examples of valid reason for ISO record rejection

## User Story

In order to know when ISO records should be rejected from the harvester pipeline, datagov wants to document examples where the reason is legitimate.

## Acceptance Criteria

[ACs should be clearly demoable/verifiable whenever possible. Try specifying them using [BDD](https://en.wikipedia.org/wiki/Behavior-driven_development#Behavioral_specifications).]

- [ ] GIVEN an invalid ISO [doc](https://data.noaa.gov/waf/NOAA/NESDIS/ncei/ncei-nc/iso/xml/C02073.xml) \
WHEN the reason is identified and it's legitimate
THEN it will be documented in this word [doc](https://docs.google.com/document/d/1hQtURlECDXdSt4Lp_kMWCxZjy8tqQJZIn_Edri5pljw/edit?tab=t.0)

## 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."
[Any security concerns that might be implicated in the change. "None" is OK, just be explicit here!]

## Sketch

[Notes or a checklist reflecting our understanding of the selected approach]