Support spaces in user input for msfdb

[dwelch-r7]

Previously having spaces in the path to framework install would result in errors running msfdb, this PR addresses that issue along with having spaces in options passed into the script

Example of current functionality, you can see when running reinit which metasploit in a folder with spaces in the name it fails to complete

and after:

Verification

• ./msfdb delete --component=all # This is destructive if you have important data in your db do this in a VM
• Create a folder with spaces in the name
• place a copy of metasploit framework in there
• ./msfdb reinit --component=all # Both components should start with no issues
• Also try with --ssl-key-file and --ssl-cert-file options where they lie in a path with a space in it

[gwillcox-r7]

Confirmed this works for the default setup and removes the need to do the workarounds mentioned in #12098 (comment) that I was having to do in order to get PostgreSQL to work on my Ubuntu 20.04 LTS machine.

Only downside is you do have to undo adding the PostgreSQL location to your path and setting the PGHOST environment variable from your workaround if you have already set these as part of your workaround efforts, but hey small tradeoff :)

[gwillcox-r7]

Alright after further conversation we did find another bug whereby if ~/.msf4/msf-ws-key.pem doesn't exist, then the reinit flag won't work as it checks to see if the file exists and fails if it doesn't. This is ironic cause the delete option will also delete this file when resetting the components so you would think that given this file is wiped during a reset that one wouldn't check it exists when resetting the database 😄

Otherwise though this PR works as expected and does what it is meant to do so I'm going to go ahead and land it in the meantime.

[gwillcox-r7]

Release Notes

Fixed a bug in the msfdb script that prevented users from being able to run the script if they installed Metasploit into a location that contained spaces within its path.