Previously collections.query_info would make an HTTP call for each resolved collection.  It now does everything in a single call to the server instead.

There is no reason to add a duplicate API for this, because get_info is identical to calling query_info with a single collection name.

The various Butler sub-objects (registry, collections) need to access the registry defaults.  Added a small helper class so that they don't need a reference to RemoteButler or each other in order to fetch the defaults.

Now that there is an independent implementation of ButlerCollections for RemoteButler, forward the equivalent Registry methods to it to reduce duplication.

Update RemoteButlerCollections to pass the new optimization parameters added in DM-45993 to the server.

When attempting to add a test for the summary_datasets parameter to ButlerCollectionInfo for RemoteButler, it turned out that it does not doing anything in the DirectButler version.

This was occurring because a caching context causes this parameter to be ignored, and the cache was always enabled in query_info previously.  This cache does not have a benefit for the new implementation.