[feature] the ability to opt a controller out of sync from commands

[caleyg]

It might be helpful to have the ability to opt-out a controller in Firestorm to not send commands to. I see this being implemented by selecting the controller in Firestorm and then having the .map() in the send command object ignore the selected Pixelblaze ids. The UI could either present checkboxes or a button labeled enable or disable depending on the state of the controller saved in the DB instance of the Firestorm server.

For my use case, I have an art piece with two Pixelblaze controllers attached to it, a Pico and a PB standard. Essentially the pico runs a border of 345 a led string that looks really good on a particular pattern that is different from what the other PB is running over 500 LEDs in the center, which I would love to have Firestorm control with the other PBs in the network.

Presently both strands are synced together if an instance of Firestorm is running in a network which might be undesirable for some.