use NonEmpty for all arguments to Queries methods where empty lists don't work

[S11001001]

There are several functions like selectContractsMultiTemplate in Queries that will always fail if given an empty input of e.g. template/predicate pairs. Currently this isn't apparent from the signature, but it hasn't been changed because the callers in ContractDao aren't trivial.

We should just percolate the NonEmpty requirement via NonEmpty types all the way back to where we parse client arguments from JSON. This might entail extending the method enrichments in NonEmpty (e.g. map is a major missing method map now exists 🎉 ), or adding overrides to the Foldable1 instance therein (also done in #11592), and of course eliminating any needless code where we handle an impossible empty-data case, starting with where we make these assertions in Queries in the first place.

With respect to #11156, any party sets should use NonEmpty too, even though the current examples use OneAnd.