Revive: Explicitly target analyze results and determine payload compatibility

[adfoster-r7]

Reviving the original work of @acammack-r7, but with updating the tests to pass - #15197

Verification

I verified that the original analyze command's verification steps still work with the import script here:
#11191

Working:

msf6 auxiliary(scanner/http/title) > db_import ~/Downloads/m3_report.xml
[... omitted ...]
msf6 auxiliary(scanner/http/title) > analyze
[*] Analysis for 192.168.18.118 ->
[*]   exploit/windows/smb/ms17_010_eternalblue - ready for testing
[*]   exploit/windows/smb/ms17_010_eternalblue_win8 - ready for testing
[*]   exploit/windows/smb/ms17_010_psexec - credentials are required
[*]   exploit/windows/smb/smb_doublepulsar_rce - ready for testing
[*] Analysis for 192.168.222.151 ->
[*]   exploit/windows/smb/ms17_010_eternalblue - ready for testing
[*]   exploit/windows/smb/ms17_010_eternalblue_win8 - ready for testing
[*]   exploit/windows/smb/ms17_010_psexec - credentials are required
[*]   exploit/windows/smb/smb_doublepulsar_rce - ready for testing

And using the new -p option with a valid match:

msf6 exploit(windows/smb/ms17_010_eternalblue) > analyze -p windows/x64/meterpreter/reverse_tcp
[*] Analysis for 192.168.18.118 ->
[*]   exploit/windows/smb/ms17_010_eternalblue - ready for testing
[*]   exploit/windows/smb/ms17_010_eternalblue_win8 - ready for testing
[*]   exploit/windows/smb/ms17_010_psexec - credentials are required
[*]   exploit/windows/smb/smb_doublepulsar_rce - ready for testing
[*] Analysis for 192.168.222.151 ->
[*]   exploit/windows/smb/ms17_010_eternalblue - ready for testing
[*]   exploit/windows/smb/ms17_010_eternalblue_win8 - ready for testing
[*]   exploit/windows/smb/ms17_010_psexec - credentials are required
[*]   exploit/windows/smb/smb_doublepulsar_rce - ready for testing

Using the new -p option with an invalid match:

msf6 auxiliary(scanner/http/title) > analyze -p payload/linux/x86/shell_reverse_tcp_ipv6
[*] Analysis for 192.168.18.118 ->
[*]   exploit/windows/smb/ms17_010_eternalblue - none of the requested payloads match
[*]   exploit/windows/smb/ms17_010_eternalblue_win8 - none of the requested payloads match
[*]   exploit/windows/smb/ms17_010_psexec - credentials are required, none of the requested payloads match
[*]   exploit/windows/smb/smb_doublepulsar_rce - none of the requested payloads match
[*] Analysis for 192.168.222.151 ->
[*]   exploit/windows/smb/ms17_010_eternalblue - none of the requested payloads match
[*]   exploit/windows/smb/ms17_010_eternalblue_win8 - none of the requested payloads match
[*]   exploit/windows/smb/ms17_010_psexec - credentials are required, none of the requested payloads match
[*]   exploit/windows/smb/smb_doublepulsar_rce - none of the requested payloads match

There was additional discussion on how to test this within the original PR:

To verify this, we will likely need to use nmap imports/db_nmap should populate at least some of the necessary information. Also needs unit testing based on nmap information.
#15197 (comment)

But I have only verified the steps that I listed previously

[agalway-r7]

Have tested the -p flag works as expected with the m3_report.xml and the output of db_nmap -O -sV -Pn --script vuln, both of which result in expected behaviour

[agalway-r7]

Release Notes

Added a -p flag to the analyze command, allowing users to specify a payload that should be considered for use with any suggested exploit modules. Output will inform the user if the specified payload can be used with suggested payloads.