In order to prevent lock ordering issues AutoGetters take locks in ascending ResourceId fashion when given a set of secondary collections.

This is also the case when yielding, as they will be acquired again in ascending ResourceId order.

However, Shard Role acquisitions sort the acquisitions in descending order of ResourceId (here as well). This has the potential to cause a deadlock even if today this isn't yet the case since there are very few users of acquisitions with multiple collections.