Cleanup filter & region parsing & validation

[Pablete1234]

Originally started to fix the /modes list command, ended up fixing way too many more things. This includes a more proper fix for the quick-and-dirty if-check added in #1050.

Monument Mode fixes:

• /mode list command sorting was still broken (initially tackled in Fix mode commands with filtered modes #1048, still broken in some conditions)
• Added current page and max page to /mode list.
• Migrated mode list pagination from legacy string-based to modern component-based.
• Tweaked ordering of mode list, started modes (or unfiltered) always first, then sorted by time, lastly sorted alphabetically.
• Modes' filter must now be dynamic & react to match changes, validated at parse time

Filter/region validation/parsing fixes:

• Adds proper dynamic filter validation, features which require a filter to be dynamic will verify that at parse time
• Validations will run after references have been resolved, this prevents unresolved-forward-references trying to perform a validation they can't yet ensure
• Unified util methods to parse regions and filters in to an XMLParser utility, that both extend. This makes a handful of unified parseProperty methods available in both RegionParser and FilterParser, with overloads for defaults, required, and validations.
• Removed the legacy String... names from region parsing, most of the times a single name is used, in the few places where multiple names are allowed they were replaced with calls that use Node.fromChildOrAttr(el, name1, name2) or similar.
• Removed dynamic filter listeners without a scope, those would listen on Filterable, which is essentially a guarantee that you'll break something. Filters need a scope to filter, they can't just filter "anything". If you're fine with "anything" simply use Filterables.scope(filter) to find what the least-specific context the filter supports listening for.
• Added line numbers to xml errors for attributes. Before attributes would only say attribute X in element Y, now they also include line numbers of the element.

Note: No PGM behavior should have changed at all. No XML changes, no run-time changes. Only more strict validation for invalid usages of dynamic filters (eg: trying to use a non-dynamic filter in a place that requires a dynamic).

Note: This has been tested with main OCC map repositories, public and private, and has not caused any new map xml error within them except for the ones i manually introduced for testing, meaning this should already be in a stable state.