Alex/driver full usage

[alex-bezek]

closes: #93

What

Instead of calculating edges and other CRDs for an ingress as it reconciles, we put it in a store with all the data and calculate the total difference of crds and then synchronize them all.

How

Uses the driver and store's methods to calculate and sync the crd differences.

Breaking Changes

Hopefully not, but probably :)

Testing

I've been running through the various combinations of ingress rules/hosts from the k8s documentation which I put into our own docs to show how edges work. So far from deleting and adding individual routes and ingresses with different annotations, I haven't hit any unexpected behaviors yet. Some potential issues like clashing routes/hosts just get merged and go away unless I'm missing a point where data can be lost. I aim to add more test to cover the core functions here especially as we change them to cover other things like default backends and wildcard hosts.
The large deletion of unit tests is because all the logic has already been re-created in the driver/store with their own tests in previous PR's, so this is just removing dead code.