Land Manager account improvements; site-filter refactor; and more...

[mradamcox]

This is a big update to how the site-filter and land manager accounts work together, and it comes along with some other updates as well.

• All new models are created in the hms app, so the old ones in fpan can be more easily deprecated.
• Create new Land Manager profiles with more unified and flexible permissions filter settings
• Create new Management Area and Management Area Group models to consolidate the previous Region and Managed Area models, and allow these to be attached to Land Manager accounts
• Big overhaul to site-filter permissions logic. Especially, consolidate all previous code into the actual search component file (site-filter.py), and refactor it significantly with an eye toward reusabilty.
• Support special permissions on multiple resource models (spurred by Public map issue #180) by fixing the iterations and ES clause additions in site-filter.
• Create new geo filter within site-filter, which uses Management Area (or Management Area Group) geometries from the ORM (which are optionally attached to Land Manager accounts) to filter search results and resource layers on the map.
• Add management command check_indexes which compares the database resources to the ES index, and attempts to reindex any that are missing
• Add management command areas with a suite of operations to manage the loading/removal of new Management Areas from shapefiles/geopackages.
• Add operation to above command that migrates all of the existing fpan.models.ManagedAreas (300) and Regions (8) into the new hms.models.ManagementArea model so they can uniformly be used for filtering.

Tickets addressed:
#180 (closed)
#159 (partial)
#127 (closed)
#173 (closed)

Tickets to re-evaluate now that these updates are in place:
#32, #61, #63, #126