Update with use of esupy for flowlist storage

[bl-young]

This implements the use of parquet storage via esupy for locally saving the flowlist and removes the flowlist parquet file from the repository

Attempting to access the flowlist will cause it to be created if not found locally.

[bl-young]

@WesIngwersen flagging you on this to ensure you are comfortable shifting to local data storage of the flowlist instead of within the repo.

[WesIngwersen]

@WesIngwersen flagging you on this to ensure you are comfortable shifting to local data storage of the flowlist instead of within the repo.

I assume it will store the flowlist parquet on the Data Commons?

[bl-young]

I can add the piece to download from data commons (I did not yet since generating locally is quite quick).
Would we prefer that by default users get the flowlist from data commons instead of generating locally?

[WesIngwersen]

I can add the piece to download from data commons (I did not yet since generating locally is quite quick). Would we prefer that by default users get the flowlist from data commons instead of generating locally?

Yes. We should go for consistency across other tools. where the principle API function to get the data in init calls in an esupy function to load from local storage or download it from the Commons if missing.

[bl-young]

ok added with c497ab6. I can confirm its working once we have a parquet up there.

[bl-young]

Assigning @catherinebirney for preparing data commons upon returning.

[WesIngwersen]

tested and works for me