Added Pandora FMS RCE and SQLi module
Implemented @jlee-r7 requested changes
Pull the copy-pasted sqli into a method
Pull the copy-pasted verification into a method
auth_succeeded? is a better name for this method
Also extract admin hash if password auth failed
Make the password hash stand out as more important
Merge pull request #1 from jlee-r7/land-2985-pandorafms-sqli

Improvements for PandoraFMS SQLi module
New module to build wordlist for use by JtR, oclhashcat, etc generated by pulling info from multiple Active Directory fields
corrections based on feedback
Detect leaked constants under Msf::Modules

MSP-11130

Detect constants leaked under Msf::Modules after the suite completes.
Log leaked constants and fail rake spec on leak

MSP-11130

Instead of printing the leaked constants to stderr, log them to
`log/leaked-constants.log`.  In task action for spec, read
`log/leaked-constants.log`.  If it exists, print each leaked constants
(and it appropriate it's module full name) and then exit with 1.  If the
file does not exist, do nothing.
Extract Metasploit::Framework::Spec::Constants.full_name

MSP-11130

Extract method to convert child constant names to module full names so
it can be reused 'Metasploit::Framework::Spec::Constants tracker' shared
context.
Filter non-loaded-module constants from leaked constants

MSP-11130

Constants from library Modules or Classes should not be reported as
leaked since they have been required and should be persistent between
spec runs.
Extract Metasploit::Framework::Spec::Constants::Suite

MSP-11130

`Metasploit::Framework::Spec::Constants::Suite` extracts out
`LOG_PATHNAME`, `configure!`, and `define_task` as those piece are
specific to handling constant leaks for the entire suite.  This is in
preparation for `Metasploit::Framework::Spec::Constants::Each`.
Detect constant leaks in individual examples

MSP-11130

`Metasploit::Framework::Spec::Constants::Each.configure!` will set up an
`after(:each)` callback that will fail the example if there are leaked
constants.  Leaked constants are cleaned up to prevent misattribution.
Metasploit::Framework::Spec::Constants cleaner

MSP-11130

Shared context will calls `Metasploit::Framework::Spec::Constants.clean
after each example.
Rename shared example file to match name

MSP-11130
Clean up leaked constants

MSP-11130
Fail `rake spec` if leak tracking unnecessary

MSP-11130

Fail `rake spec` if
`Metasploit::Framework::Spec::Constants::Each.configure!`'s
`before(:each)` does not clean all leaked constants and if should be
removed so that it does not interefore with future specs.