issue #19450: refresh caches/pickers when a setup model changes

A few comments on this incident:
-I am not using isAutoSync as a property on XM.Collection, because every cache should bind to the relational datastore. Right?
-There are a surprising lack of comparators for our collections. There is an orderAttribute attribute that's not used much and only informs the query. By my thinking, the collection for every XM.Document should by default sort by the document key. I imagine we don't want to need to pass in an order attribute when making the cache, because we should just set up comparators for all the collections. Right?

Don't pull in the pull request until these issues have been resolved. I've left some pertinent code commented out that I'd like to delete, or actually use, depending on what we decide.