Issue 46 balrog sync

[rhelmer]

@rdalal Putting this up for discussion to make sure it's the direction we want to go - note the FIXMEs :) Some more context below, but just hoping to know if this is the sort of thing you had in mind.

I just did the bare minimum to get the existing "Sync" button to work in React for local testing purposes, I did not attempt to move it from its current location so that still needs to be done.

After discussion with @mozbhearsum in IRC earlier:

• https://bugzilla.mozilla.org/show_bug.cgi?id=1315801 for filtering rules by product name on the Balrog side
• consider using a field other than comment for Morgoth metadata - @mozbhearsum suggested that alias might be workable

We also discussed whether removing all Morgoth-created rules was the right thing to do - I agree that it's not ideal, but for an MVP it's reasonable.

Once we have Balrog reading and sync diff sorted out I think it'll be easy to fix it so that we only remove and modify releases+rules where needed.

[rhelmer]

Some notes from in-person review w/ @rehandalal

• [ ] there will be a "sync to QA" and a "sync to release" button, which will pass the channel in the release object. this should be added to the blob sent to balrog
• [ ] needs to actually post to balrog (mock it for now, later circle CI could run a balrog instance perhaps)

[Osmose]

I suspect this is not necessary anymore what with #65 and all. Closing.