Add option/possibility to set fuzzy for the whole plugin dependency.

[WenzDaniel]

We should add beside the already existing fuzzy_for option an option which allows to ignore Option/Versions changes for the whole dependency graph of a plugin. I just had the case that someone was trying to load older 1T data for which multiple plugins changed see some print out below:

Plugin energy_estimates is stored with verison 0.1.0 and current context version is 0.1.0
Plugin event_basics is stored with verison 0.5.3 and current context version is 0.5.3
Plugin event_info is stored with verison 0.0.0 and current context version is 0.0.0
Plugin event_positions is stored with verison 0.1.1 and current context version is 0.1.2
Plugin events is stored with verison 0.0.0 and current context version is 0.0.0
Plugin lone_hits is stored with verison 0.3.0 and current context version is 0.3.7
Plugin merged_s2s is stored with verison 0.0.0 and current context version is 0.0.0
Plugin peak_basics is stored with verison 0.0.5 and current context version is 0.0.8
Plugin peak_positions is stored with verison 0.1.0 and current context version is 0.1.0
Plugin peak_proximity is stored with verison 0.4.0 and current context version is 0.4.0
Plugin peaklet_classification is stored with verison 0.2.0 and current context version is 0.2.0
Plugin peaks is stored with verison 0.1.1 and current context version is 0.1.1
Plugin pulse_counts is stored with verison 0.2.0 and current context version is 0.2.2
Plugin raw_records is stored with verison 0.0.0 and current context version is 0.0.0

[JelleAalbers]

Maybe adding a context method / strax function that implements the solution from https://youtu.be/Iagx1MHCD7Y?t=2751?