Adding SimEnergyDeposit filter module for systematics studies (v09_89_01_01, release/SBN2024A

[jzettle]

Description

Please provide a detailed description of the changes this pull request introduces. If available, also link to a docdb link where the issue/change have been presented on/discussed.
Enabling filtering of SimEnergyDeposits around z=0 to capture the effect of not directly simulating a structure that holds the two sections of the ICARUS ind1 plane together at z=0. Does not affect the nominal simulation and this is geared towards ICARUS systematic variation studies. Identical code changes towards the develop branch were reviewed and approved in #486 and this code was developed using the release tag v09_89_01_01 in the first place. Testing this version gives the expected filtering behavior on a set of a few events. This correctly includes only the 4 commits that are directly part of this request and the previous approval process.

• Have you added a label? (bug/enhancement/physics etc.)
• yes
• Have you assigned at least 1 reviewer?
• yes, this code was approved in Adding SimEnergyDeposit filter module for systematics studies (mostly geared towards ICARUS but also general to both detectors) #486 so see that for the approval chain.
• Is this PR related to an open issue / project?
• yes, this is geared towards the issue Gap in tracks at boundary of induction 1 plane icaruscode#769
• Does this PR affect CAF data format? If so, please assign a CAF maintainer as additional reviewer.
• no, but @PetrilloAtWork reviewed it anyway on my request and has approved it
• Does this PR require merging another PR in a different repository (such as sbnanobj/sbnobj etc.)? If so, please link it in the description.
• yes, there is a companion icaruscode PR here: Implementing SimEnergyDeposit Filter for z = 0 in the production release icaruscode#780 that has configurations needed in order to run this in the ICARUS simulation
• Are you submitting this PR on behalf of someone else who made the code changes? If so, please mention them in the description.
• no, but the work was done with support from @jzennamo