Ingest neutrino candidates from IceCube

There is a bit of interest in incorporating IceCube alerts, which would require the following:

• Figure out how to ingest alerts, If needed, create/modify GCN or Kafka listener to ingest events from IceCube
• Ensure IceCube events can create external events either in their current form or with some wrapper function (i.e. get example GCN notice or equivalent and see if can be uploaded directly)
• Determine exactly which notice types to listen to
• Contact GraceDB developers to add pipeline='IceCube' if not already available (see this issue: computing/gracedb/server#255 (closed))
• Modify neutrino/SNEWS listener if similar enough to current workflow in order to fully include in RAVEN pipeline.
• Determine expected rate (#/year) of detected alerts and whether the individual significance (FAR?) of the events are available or relevant (e.g. is very high significance so that FAR_neutrino << FAR_GW?).
• Determine how the sky localization could be downloaded from the experiment or created via existing tools in gwcelery
• Add relevant values to RAVEN pipeline (time window, raven.trigger_raven_alert) and add exceptions when different from standard workflow
• Add testing via pytests, internal MDCs, and/or O3 replay to ensure system works as expected
• Add or modify circular template(s) in ligo-followup-advocate to display info about such coincidences

Example alerts:

ivo___nasa.gsfc.gcn_AMON_ICECUBE_BRONZE_Event2024-01-23T11_25_36.05_25_138890_034080563_0

ivo___nasa.gsfc.gcn_AMON_ICECUBE_BRONZE_Event2024-01-23T11_25_36.05_25_138890_034080563_1