Fix issues caused by ITERM appdef

28ebcbc added a custom appdef for iTerm2.

That appdef allowed us to make certain keymappings effective *only* in
iTerm2. (Good! That's what we wanted.)

That appdef appears to have had an unintended side effect: It appears to
have *removed* iTerm2 from the "TERMINAL" appdef. (Whoops! That's not
what we wanted.)

Since the "TERMINAL" appdef is used both in my private.xml and in
keymappings defined by KeyRemap4MacBook, 28ebcbc caused serveral
keymappings to stop working in iTerm2.

For all keymappings that previously specified "TERMINAL", they now need
to specified both "TERMINAL" and "ITERM".
In (S)uper (D)uper mode, use MM to copy line

This is similar to yy in Ubiquitous Vim mode. [1]

We have to use lastpressedphysicalkey_only to trigger this behavior
when the previous key pressed was M. For the reasons described on the
mailing list [2], we can't use DoublePressModifier for this mapping.

[1]: https://github.com/tekezo/KeyRemap4MacBook/blob/74d57c84b0/src/core/server/Resources/include/checkbox/ubiquitous_vim_bindings/core.xml#L871
[2]: https://groups.google.com/forum/#!searchin/keyremap4macbook/jason/keyremap4macbook/x_3gwaANz3w/shllHiCEqsEJ