Decommission IceFlow

[asteiker]

This Issue encapsulates all work required to fully retire IceFlow including its backend components, including:

• Updating the existing corrections notebook to demonstrate how to apply CRS transformations on existing IceFlow-supported datasets.

• Execute decommissioning of IceFlow including Valkyrie orders and and IceFlow library/client.

[trey-stafford]

In our discussion yesterday, we talked about potentially archiving the Valkyrie database (estimated to be ~5TB in size). We think the database has limited/no value, and we would want to start from source data files to create a new harmonized data product rather than pull from the database.

I think we can safely delete the database after we shut down the valkyrie services, but we could archive the database for some period as a precaution.

[trey-stafford]

#78 removes most of the code/notebooks from iceflow. We will address updating the existing corrections notebook with a real-world example in #76