Remove rob set caching from DataProviderTools

I remove the rob sets that prevent repeat decoding from the DataProvidersTools, in the trigger 'views' system we want to use identifiableContainer caches to avoid repeat decoding based on the per hash level. Currently we are seeing inconsistent results and believe the rob set caching is causing conflict.

@oda @goetz @stsuno @sutt @zgrout Can we remove this rob set check? Do you foresee any problems in other areas?

Edited by Adam Edward Barton

Merge request reports