Error in North Carolina COVID data reporting results in negligible (zero) risk for every activity.

[LearnByWire]

Describe the bug
The state of North Carolina has an error in their October 19th reported data which results in the number of COVID cases showing up as zero. This error is causing ALL Microcovid calculations for the state of North Carolina to come back as negligible (near zero) risk. The reporting error is documented on the state DHHS website and will be resolved when they next report data on October 26th: https://covid19.ncdhhs.gov/dashboard "Note: Dashboard and report updates were not published Oct. 19 due to a technical issue. Please check back Oct. 26, 2022 for the next update. Full dashboards and reports will include the Oct. 19 data next week."

Link to microCOVID scenario
Being in a crowded grocery store maskless for an hour is being reported as "Very Low Risk" for an individual on the highest caution budget. https://www.microcovid.org/?distance=sixFt&duration=60&interaction=oneTime&personCount=10&riskBudget=1000&riskProfile=average&scenarioName=60minShoppingCrowded&setting=indoor&subLocation=US_37183&theirMask=none&topLocation=US_37&voice=normal&yourMask=none&yourVaccineDoses=3&yourVaccineType=pfizer

To Reproduce
Steps to reproduce the behavior:

1. Do any risk calculation using the state of North Carolina/its component counties as the location.

Expected behavior
Based on a risk calculation I performed last week where furniture was being delivered to my home, I expected the calculation I ran to have moderate risk, but any variation came back as virtually no risk because the number of cases is incorrectly being reported as zero.

Is this a regression?
The last time I used the calculator was Monday, October 17th, and it did not have this problem. The error in North Carolina's data set is from October 19th.

Additional context / screenshots
Add any other context about the problem here, including any screenshots.

[apiology]

Thanks for the report, @LearnByWire! Yes, I've seen this as well in different locales. There's some context here around this, with information on how folks can help to resolve issues like these: #1626