remove type field for some settings in the rule editor

this seems like a convoluted way to define a method.

I would be tempted to define this stuff in something that isn't a set module, because that way we're not adding all these things as instance methods on settings cards where we don't really want them.

if it were, say Card::Setting (which I'm not pushing for), it could look like this:

```
class Card
  module Setting
    def set_setting_opts
      ...
    end
  end
end
```

and then when you call `extend Card::Setting`, it would do the same as above.  And it's actually more efficient in code terms, because the methods only defined once.  (that's a paltry gain, but if it's cleaner and faster, what's the argument against?)