Migrate OGDUtils into other packages, or remove completely orphaned code #4
Description
This has never really been useful as its own package, except as the risk-free first attempt at creating something as a package.
The actual code in the repo is mostly just a dumping ground of things from past projects.
There's a few classes/functions that have potentially-useful-ish functionality for dealing with parsing out certain features from a big feature file, or generally encode obtuse DataFrame operations into nicely-named, meaningful functions. These would probably be better in ogd-common, if anywhere.
Mostly, though, it's things like project-specific workflow setup code from the old Lakeland clustering and Jo Wilder script experiment projects, or similar. That could mostly be moved out into dedicated research project repos, where the code is free to sit and bitrot.
There's also the old VRTeX code for "VR Telemetry eXtraction", which hasn't done much for us yet, but could conceivably become ogd-core built-in extractors for use with VR, for example. Other bits could go into the ogd-samples for nice VR templates.
Last option would be to give OGDUtils a name that more-nicely aligns with naming conventions as e.g. ogd-utils, with the specific utils being for working with DataFrames of feature data, and ogd-utils could then be imported into ogd-samples notebooks. All that said, though, there's not much reason to do this that wouldn't be equally a good option in ogd-common.
Anything that doesn't fit into any of the above possibilities, should just be removed.