Update msfcli to use HasActions
Datastore options should default to TLS1, not SSL3

Otherwise, we risk getting our connections killed by particularly
aggressive DPI devices (IPS, firewalls, etc)

Squashed commit of the following:

commit 5e203851d5c9dce1fe984b106ce3031a3653e54b
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Wed Oct 15 10:19:04 2014 -0500

    Whoops missed one

commit 477b15a08e06e74d725f1c45486b37e4b403e3c2
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Wed Oct 15 10:16:59 2014 -0500

    Other datastore options also want TLS1 as default

commit 8d397bd9b500ff6a8462170b4c39849228494795
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Wed Oct 15 10:12:06 2014 -0500

    TCP datastore opts default to TLS1

    Old encryption is old. See also: POODLE
Land 4022, datastore should default TLS1 vs SSL3
Revert #4022, as the solution is incomplete

Revert "Land 4022, datastore should default TLS1 vs SSL3"

This reverts commit 4c8662c6c1171c8ccc161ed90aa144ba29e7de3b, reversing
changes made to 0937f32ff9b9f3d150bb2caea12f21a845dd730c.
Unland #4022 with #4023 (more discussion)
essage aborts
Allow non-SSLv3 Meterpreters (auto-negotiate)
Land #4025, auto-negotiate meterpreter SSL
Land 4006, msfcli support for show actions