Add conditional option validation depending on SESSION/RHOST connection

[dwelch-r7]

The new session types allows certain modules to connect over either RHOST or an existing SESSION but this meant when normally the RHOST option was required the be set that could no longer be the case leading to a compromised user experience since we were no longer communicating which options needed to be set

This PR resolves that by adding conditional validation of options depending on the chosen connection type so for example if you want to connect via RHOST we also check (where applicable) that RPORT or the USERNAME is set. Then when a connection is made over an existing SESSION we can still allow the user to only set SESSION and not worry about the missing values only required for a new RHOST connection

Validation Steps

• Use a module that supports the new session types
• Check that when SESSION is set no option related to RHOST are forced to be set
• Check that SESSION doesn't need to be set when connecting via RHOST
• When attempting to connect over RHOST and RPORT/USERNAME/etc aren't set the user is notified of all missing required options
• When neither SESSION nor RHOST is set there is a warning telling the user this

Note: Some options can be an empty string so if you unset OPTION and don't get the expected outcome you may need to do set --clear OPTION

[cgranleese-r7]

Testing against Windows 10 via new SMB session type and everything seems to be working as expected 👍

Check that when SESSION is set no option related to RHOST are forced to be set

Check that SESSION doesn't need to be set when connecting via RHOST

When attempting to connect over RHOST and RPORT/USERNAME/etc aren't set the user is notified of all missing required options

When neither SESSION nor RHOST is set there is a warning telling the user this

[cgranleese-r7]

Release Notes

This PR adds conditional validation of options depending on the chosen connection type, so for example if you want to connect via RHOST we also check (where applicable) that RPORT or the USERNAME is set. When a connection is made over an existing SESSION we can still allow the user to only set SESSION and not worry about the missing values only required for a new RHOST connection.