Some sr3/sr3d actions don't make sense on a cluster

While working on #1 I realized that some of the possible actions for sr3 don't make sense on a cluster.

sr3d currently doesn't do any kind of filtering. Maybe it should?

- edit: if this were to do anything, it should edit the local copy of the config (and maybe `sr3_commit` it). But it shouldn't run on the remote nodes.
- add
- remove: maybe this should alias to sr3_remove? sr3_remove currently only supports one config at a time
- convert
- foreground
- run

Start by reading the sr3d action handling and the related sr3_remove and sr3_commit behavior mentioned in the issue, along with the context from #1. Determine which actions should be filtered or redirected when operating on a cluster, then verify that edit, add, remove, convert, foreground, and run no longer perform inappropriate remote work.

Written by the indexing model from the issue text.