Partial Configurations should support validating ExclusiveResource reservations during publish or pull
In the current implementation for Partial Configurations, the ExclusiveResources in the configuration fragment can be used to reserve resource modules or resources to a specific fragment. However, this is not validated until runtime. So, if there are two fragments that are using same resource modules and one fragment has those resources exclusively locked, the configuration enact will fail during runtime.
These exclusive resource reservation checks should be done either at the publish time (push) or before enacting the configuration after a pull is complete.