Compliant Checker report: [TIME003] rejects valid year-only (YYYY-YYYY) time range for yearly (Oyr) files

[rhaegar325]

Summary

The WCRP CMIP6 compliance check [TIME003] Check Time Range vs Filename fails on a
correctly-named yearly ACCESS-ESM1-5 file:

[TIME003] Check Time Range vs Filename
* No time range token found in filename, but frequency='yr' requires a time range
  (e.g. '_YYYYMM-YYYYMM.nc' or '_YYYYMMDD-YYYYMMDD.nc').

The file in question:

no3_Oyr_ACCESS-ESM1-5_historical_r1i1p1f1_gn_0101-0110.nc

The time-range token 0101-0110 (YYYY-YYYY) is the correct format for yearly
(Oyr, frequency yr) data. The check only accepts tokens of at least YYYYMM
granularity, so it does not recognise the year-only token and reports it as missing.

Expected behaviour

For ACCESS-ESM1-5, Oyr filenames must not include a month — the time range is
year-only, YYYY-YYYY:

no3_Oyr_ACCESS-ESM1-5_historical_r1i1p1f1_gn_0101-0110.nc   ✅ correct
no3_Oyr_ACCESS-ESM1-5_historical_r1i1p1f1_gn_010101-011012.nc   ❌ wrong (has month)

At this stage, it is not clear which standard should be applied. This error may be an issue with the Compliance Checker itself.