Fix a bug that deleted too many hosts

When running a command that takes host ranges as arguments (e.g.,
`hosts`, `services`), the arguments get parsed by
Rex::Socket::RangeWalker. If RangeWalker was unable to parse, it would
return nil, which in this context means "all hosts." If the user is
searching, they get all hosts instead of the ones they were interested
in -- this is annoying, but not too big a deal. Unfortunately, the same
logic applied when *deleting* hosts, with `hosts -d ...`, causing all
hosts to be deleted when giving it an invalid range.
Fix @todb-r7 feedback
Fix lying documentation
minor change
changed openemr_sqli_privesc_upload according to suggestions
changes made to astium_sqli_upload based on suggestions
CVE-2013-5696 RCE for GLPI
corrected some codes requested by Meatballs
Bumping out deprecation date

Pray I don't alter the deprecation date further.
Revert "Bump requirement for packetfu"

This reverts commit a2f0834877bb05ea8725407ae7a41bb20007c2c3.

This is an errant commit, already implemented in #2361
Fix possible port conflict
Add Context to rex sockets plus track them with add_socket
Use payload.encoded because BadChars are defined
Add module for MS13-071
Merge remote-tracking branch 'upstream/master'
Add minor cleanup
Added minor indentation updates
Land #2386, don't accidentally delete all hosts
Land #2358, deprecate funny names
Clear report_data on each host report