WIP: Generalize properties to constraints

[frenchy64]

Merge first: #1029

In prototyping phase. Overall goal is to obviate the need for :and, :not, and :fn schemas, in particular because of their brittle generators. It also leads more more relevant error messages #1001.

TODO

• validate
• explain
• generate
• transform
• parse
• merge/union

Ideas:

• (Noah) allow :or property [:map {:or [:a :b :c]} ..]
• rename :keys to :keyset
• enhance :set with the same properties for heterogeneous sets
• enhance :map-of with keyset constraints
• generalize beyond keysets, just call them "constraints".
• rename :keyset to :and.
• integer constraints [:int {:> 5 :< 10}], easier to generate than [:and :int [:> 5] [:< 10]].
• make :min :max constraints so they can participate in constraint resolution
• extend to :double
• take :gen/min :gen/max into account earlier during solution generation
• perhaps :gen/and :gen/or etc?
• :string constraints
• extend humanize output to structure logical operators explicitly ("should either a or b" => [:or "should a" "should b"])
• :dispatch constraint

[:multi {:dispatch :db/valueType}
 [:db.type/tuple [:map {:xor [:db/tupleType :db/tupleAttrs :db/tupleTypes]}
                  [:db/tupleType {:optional true} ...]
                  [:db/tupleAttrs {:optional true} ...]
                  [:db/tupleTypes {:optional true} ...]]]]
==>
[:map {:dispatch [:db/valueType
                  [:db.type/tuple [:xor :db/tupleType :db/tupleAttrs :db/tupleTypes]]]
                  [:db.type/string ...]
                  [:db.type/ref ...]}
 [:db/tupleType {:optional true} ...]
 [:db/tupleAttrs {:optional true} ...]
 [:db/tupleTypes {:optional true} ...]]