Data Mapping App: Update app to to be model dependent

Add a selector at top of control panel for model. This should simplify how the data mapping app works and will limit the data that can be shown to that which is relevant to the selected model. Note, however, that some datasets will be the same over multiple model editions, but that should not be the concern of this app, the services it relies upon will return whatever is relevant and available. This broad issue describes the overall goal but may warrant subdivision into smaller sub-issues.

• The models available will be the same as for which 'dynamic' hazard calculations can be performed.
• Given a model, there will be a region and a year or tag (not sure which of these two will be better to use) that can be used to query various services.
• Example: Given nshm-conus 2018 (tag: 5.1.*), the sites service would be queried for ?region=conus
• Example: Given nshm-alaska 2007 (tag: 1.1.*), the fault sections service will handle getting the correct fault sections for the state of AK. In this case the fault sections service will likely load more than one tag from nshm-fault-sections.