Anonymize dependencies during packing
Switch on 'anonymous' dependency packing -- with this option, there are two types of TES objects packed:
- those that are explicitly (directly) requested (because eg. a trigger line requests a certain (list of) TES location(s), or they are 'always' requested (such at MC relations))
- objects which are referenced by other objects already selected to be packed
With this MR, 1. can be requested to be unpacked, and if in doing so, items from 2. are needed, those will be put in the TES in some 'anonymized' location, as typically not the entire container was packed (because then they would be in category 1 by construction). As such, the (unpacked) containers in 2. can not be used 'as if' they were the (entire) original content of the TES at the moment of writing -- only those elements (indirectly) referred to by objects from 1. will appear. Hence the TES location of the objects in 2. is irrelevant, and if they would appear in the same location as when the data was written would generate false expectations of their content.
Goes together with LHCb!4136 (merged) and LHCb!4149 (merged)