feat: Add unit-test to check consistency of Notice field names.

[bdferris-v2]

While working on better alignment of code and documentation as part of #1324, I fixed a few inconsistent field names (e.g. filename vs fileName). But I also wonder if we could catch these inconsistencies earlier. This PR provides a unit-test that checks all Notice field names against a manually curated allow-list.

Any time a new field name is added, this unit-test will fail. When that happens, we hope the author will do one of the following:

1. See there is an existing field name that might be more appropriate to use.
2. If not, add their new field to the allow-list.

Please make sure these boxes are checked before submitting your pull request - thanks!

• Run the unit tests with gradle test to make sure you didn't break anything
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• Linked all relevant issues

[bdferris-v2]

@isabelle-dr curious to get your thoughts on this

[github-actions]

✅ Rule acceptance tests passed.
New Errors: 0 out of 1419 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
Dropped Errors: 0 out of 1419 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
0 out of 1419 sources (~0 %) are corrupted.
Commit: 1b563ee
Download the full acceptance test report here (report will disappear after 90 days).
✅ Rule acceptance tests passed.

[isabelle-dr]

Great addition! Can we see what it looks like when the test fails?

[bdferris-v2]

Ideally, a developer would run gradlew test before submitting their PR (per the instructions) and get a failing unit test that would look like:

In this example, csvRowNumberA and csvRowNumberB are the new unexpected fields (artificial example). At that point, the developer would hopefully go look at NoticeFieldsTest. testNoticeClassFieldNames, see the instructions there, and either change their field names or update the test.

[davidgamez]

LGTM!

[github-actions]

✅ Rule acceptance tests passed.
New Errors: 0 out of 1423 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
Dropped Errors: 0 out of 1423 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
New Warnings: 0 out of 1423 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
Dropped Warnings: 0 out of 1423 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
0 out of 1423 sources (~0 %) are corrupted.
Commit: 592b853
Download the full acceptance test report here (report will disappear after 90 days).
✅ Rule acceptance tests passed.