Move weather into JSON

[Ramza13]

Summary

SUMMARY: Infrastructure "Move weather from being hardcoded into json."

Purpose of change

Part of setup for #41067
Hardcoded = bad
Allow ability via json to add. delete, or change all weather.

Describe the solution

Added weather_types and weather_types.json. Weather_type defines the behavior and types of weather. All references to specific weather in code have been replaced by references to weather properties and the weather enum has been replaced with a vector. Regional_map.json now contains a list of weather ids allowed. No functional changes other than one minor change to some weathers rate of extinguishing torches.

When deciding the weather this array is iterated over and each elements requirements are tested, the last entry with valid requirements is chosen. At the moment requirements are what the existing weather used, such as humidity, temperature, pressure, or another weather being true already.

Updated documentation

Describe alternatives you've considered

Testing

Used debug conmmands to generate weather test data, set various weathers and observe results.

Additional context

Future PRs are planned to expand both requirements and weather effects. Providing freedom to make weather depend on random events or time intervals and cause all effects and or monster spawns, injury, radiation.

[anothersimulacrum]

Great job!

[ZhilkinSerg]

Damn :)

Can you please make weather_type a distinct json object (similar to what I did in my branch linked above), so you could just reference in regional settings by id instead of putting full definition there.