Feature omniring

[reyvababtista]

This PR adds OmniRing data storage feature into the backend. More information about OmniRing can be found here: https://www.cse.psu.edu/~mkg31/projects/omniring/

[biblicabeebli]

I don't seem to be able to change the target branch..... hmmm....

[biblicabeebli]

Ok, there we go, ui always throws me on that. Onto review!

[biblicabeebli]

Generally looks fine, couple instances where I need you to clean up the scribbled-on whitespace.
One file I genuinely can only see whitespace changes in and need you to revert or tell me what changed.

I will need to stick a couple pieces behind a feature flag, handle a merge migration for anything other database changes since original merge request - I'll happily do that.

Making a new target branch for this so it doesn't go right to staging, we will target that branch, keep it up to date with staging.

I can revert the whitespace myself, I'd rather not, I do need you to get a handle on your IDE's aggressive autoformat. Cleanup is good, autoformat tools can be really helpful, aggressive autoformat is not because it screws up git history.

[biblicabeebli]

base updated to reyva/omniring, currently equal with staging.

[biblicabeebli]

(trying to be helpful about your whitespace issues, might sound passive agressive, that is not the intent)

If you are using the command line for git diffs you can add this parameter (there is a third option, context, it seems.... dumb; and also a none ):

• --ws-error-highlight=new,old

or you can permanently add it to your git config with

• git config diff.wsErrorHighlight new,old
  (no idea if this is respected by non-cli interfaces, but it might be).

This setting will help you review whitespace in your diffs.
I recommend defaulting to a view that includes whitespace changes in your default view, and having a backup command line alias with --ws-error-highlight=none