Move pry and irb commands to developer dispatcher

[wvu]

We also fall back on prying Framework if a module isn't active.

This fixes the following bad behavior:

msf5 > pry
[*] exec: pry

And then your input gets stolen.

• Test help and see pry listed
• Test help pry and see pry help
• Test pry in a module context
• Test pry in any other context

msf5 > use exploit/linux/http/hp_van_sdn_cmd_inject
msf5 exploit(linux/http/hp_van_sdn_cmd_inject) > pry
[1] pry(#<Msf::Modules::Mod6578706c6f69742f6c696e75782f687474702f68705f76616e5f73646e5f636d645f696e6a656374::MetasploitModule>)>
msf5 exploit(linux/http/hp_van_sdn_cmd_inject) > back
msf5 > pry
[1] pry(#<Msf::Framework>)>

[wvu]

Release Notes

This moves the pry and irb commands in msfconsole into the developer command dispatcher, grouping all development-related commands together for better accessibility. This also fixes a misfeature where running pry outside a module context would hang. Now a Pry session is started in the Framework context.