Integrity issue for LFPBandSelection

[samuelbray32]

Describe the bug

• Rather than an ElectrodeGroup table, the LFPBandV1 pipeline stores/selects electrodes with the part table LFPBandSelection.LFPBandElectrode
• In the tutorial users are directed to use LFPBandSelection.set_lfp_band_electrodes to create the selection entry
  • If there is an existing entry for the LFPBandSelection key they're using, and they specify additional electrodes not in the original entry this will add those electrodes to the part table
  • If LFPBandV1 was already populated for the selection entry, there is now a mismatch between the entries in LFPBandSelection.LFPBandElectrode and what is calculated and stored in LFPBandV1

Short Term Fix

• In LFPBandSelection.set_lfp_band_electrodes , check if existing LFPBandSelection entry.
  • If so, if the specified electrodes don't match what is already in the part table, raise an error/warning and don't insert

Longer Term Fix

• Above solution does not allow creation of new LFPBandV1 entry with different electrode selection for a given LFP + filter combination. Can be an issue if original entry was only made for a small subset of electrodes.
• Issue comes from combination of the concept of a Selection table and a Group table in LFPBandSelection
• Would suggest separating in any future pipeline version

[edeno]

I can add this to #1280