TrigNavigation: fix deserializaton/thinning of Run-1 navigation
In !43270 (merged) caching of deserialized navigation blobs was implemented. However, when multiple navigation instances are used the corresponding holders also need to be cached and registered in each navigation instance.
Also throw an error in the thinning service in case the list of holders in the navigation is empty. This should never happen and would point to an issue in the initialization of the navigation.