Simplify Names and UI

[djay]

Currently the settings seem very technical and hard to understand what they do or how to use filters.
I've attempted to some changes to try fix some of these problems

• rearranging fields in settings to put the most useful (and easiest to explain) items first
• moved advanced/technical options to the end... could also move to to an advanced tab
• rewrote much of the descriptions to use more end user understandable language (e.g. Index is not an end user understood term. neither are AND/OR logic operations)
• changed names to reduce confusion that filters can be used for more than just collections if Tests for tiles + support contentlistingtiles without collections #133 is accepted.

Here is an example of the current state

Name changes

Here are some of the major ones

• "Collection Filter" -> "Result Filter"
• "Collection Search" -> "Result Search"
• "Collection Filter Result Sorting" -> "Result Sort"
• "Collection Maps" -> "Filter by Map"
• "Group by" -> "Filter by"
• "filter group" -> "filter option"
• "filtertype_single" -> "One Option at a time"
• "filtertype_and" -> "Reduce Results (AND)"
• "filtertype_or" -> "Expand Results (OR)"

TODO

• rewrite the readme to explain how to use collectionfilter.
• find better name. "Results" is probably not a good name, esp if you use a filter mosaic contentlistings for folder listings which aren't really search results. Maybe "Listing Filter"?
• The combinations of Input Type, Filter Type and narrow down is still confusing to understand what you will get in the end. There must be a simpler way to present the choices
  • if you choose multiple you get checkboxes not radio or dropdowns
  • it's hard to explain what narrow down means. does narrow down when using OR even make any sense?
• it's not very clear when a user would want to choose a different target, CSS selector or resulting listing view name.