guard persist on handler existence

[jmartin-tech]

Short term fix to only persist jobs with handlers. More work should
be done to improve job persistence to allow more jobs types to persist.

Verification

List the steps needed to make sure this thing works

• Start msfconsole
• use exploit/multi/handler
• set LHOST <IP_ADDRESS>
• set payload windows/meterpreter/reverse_tcp
• run -j
• jobs -P
• use socks_proxy
• `set LHOST <IP_ADDRESS>
• run
• jobs -v
• jobs -P
• Verify all command complete successfully (second jobs -P will report socks_proxy job is not a handler)

[jmartin-tech]

Note for future travelers, auxiliary module set context values in the ctx array position expected to contain the handler details. This results in undefined behavior when code expects ctx[1] to be handler details.

Job context should be more explicit and ctx should probably be either be a hash with known keys or an object with accessors

[zeroSteiner]

Looks perhaps related to #13593 (which has a corresponding PR).

[mubix]

This fix worked for me. Thanks!

[dwelch-r7]

Looks good to me!

[dwelch-r7]

Release Notes

Fixed a crash related to the verbose output of jobs with jobs -v, and persistence of jobs with jobs -P, when auxiliary jobs were present.