Improves UX for scanner/login modules

[cgranleese-r7]

This PR adds support for a summarised output to the end of login/scanner modules within Framework. The idea was that some scanners are either way to quite or way too noisy. So this implementation aims to add a module option that will be enabled by default but is configurable by the user, which will dictate if the table will be output or not.

Example output

When targeting a single host, the scanner is too quiet. Logic was added to check for when a single user is passed and change to verbose mode.

Verification

• Start msfconsole
• Use a login module
• Test against a single host
• Test against multiple hosts
• Verify the table is output by default
• Verify the table is not output when ShowSuccessLogins is set to false
• Verify the module outputs the verbose output when ran against a single host

[adfoster-r7]

Not a blocker; This might still need opt out functionality, were folk do want a quiet scanner still for 1 target

[adfoster-r7]

This might be used in contexts that aren't related to bruteforcing anything; so maybe we need to use different terminology here

[cgranleese-r7]

Went with scan, let me know if that works, or if you had something else in mind.

Suggested change

	print_status("Bruteforce completed, #{logins.size} #{logins.size == 1 ? 'credential was' : 'credentials were'} successful.")
	print_status("Scan completed, #{logins.size} #{logins.size == 1 ? 'credential was' : 'credentials were'} successful.")

[adfoster-r7]

Just to make testing easier, can we grab in this commit into this PR? #19220

[adfoster-r7]

Release Notes

Updates brute force modules to output a summary of the credential discovered. This functionality is currently opt-in with the feature set show_successful_logins true msfconsole command