Rethink LCWIPs in browse tool

[dabreegster]

We should consider making LCWIPs their own layer, not part of the scheme data that's loaded automatically. Some reasons:

• it's semantically very different from the ATF data
• it's growing in size a fair bit
• it has special fields that we should be able to show / filter / color by, so maybe deserving its own controls

and a feature request to open the PDF associated with a scheme. We could upload these to GCS as well, but unsure how much work it'll be to match up schemes to the PDFs

[dabreegster]

Related to #483 as well -- Did some hunting around for ideas about filtering. As a real use case, we needed to build an OR earlier today -- two boolean fields or presence of a boolean within nested funding sources. https://ux.stackexchange.com/questions/1737/intuitive-interface-for-composing-boolean-logic and https://querybuilder.js.org/demo.html for ideas