173 filter invalid area names

[i-be-snek]

In this PR:

• Invalid country names like "country1" or "Location 2" where the model is hallucinating its own instructions are filtered out.

• Filtered-out locations appear in the log as errors when parsing events

   normalize_locations: 2024-10-30 16:56:08 ERROR    Input area=country2 type=<class 'str'> is not a valid area name
   normalize_locations: 2024-10-30 16:56:08 ERROR    Input area=country2 type=<class 'str'> is not a valid area name

To test this PR, try:

• Modifying an llm output file and swapping some admin areas and location names to "Country22" or "Administrative Area3", then parse the file to ensure they are filtered out

[i-be-snek]

@liniiiiii this can be reviewed whenever. But if #183 passes and makes it to main first, then I'll rebase this on main. 😃

[liniiiiii]

@liniiiiii this can be reviewed whenever. But if #183 passes and makes it to main first, then I'll rebase this on main. 😃

@i-be-snek , I reviewed #183 and approve that pr, could you rebase this pr, I will review later, thanks!

[i-be-snek]

@liniiiiii done! it's ready for a review now :)

[liniiiiii]

After testing with manually adding some wrong "Location1" and "Adminstrative_Areas1" in the raw file, the parsing process correctly filtered them out in L1, L2 and L3. Approved this pr to main branch, thanks!