Remove rubocop and msftidy touchpoints

This replicates PR rapid7#3639 for the staging/electro-release branch

Rubocop replaces the default YAML library which makes development
testing difficult. It does not cause problems on Travis, but according
to reports, it does cause instability with many individual dev
environments.

While I would love to have a more solid source of this bug report, right
now this was an oral report from @shuckins-r7 (who I tend to believe a
lot).

(Conflict resolved on rubocop.yml)
Merge pull request #3641 from limhoff-r7/bug/MSP-11046/resource

MSP-11046 #land
Merge branch 'staging/electro-release' into feature/MSP-10992/scanner-dry
Make sure which the full payload is used
Merge branch 'electro-remove-rubocop' into staging/electro-release
Fixed 'execute_command()' missing 'opts' parameter
Update Gemfile.lock as well for PR #3639
Fix (properly) 'execute_command()' missing 'opts' parameter
Give a chance to the mixin
always set our rails root to our root

this works fine when calling any framework binaries
from their path as CWD. if you call tehm from another path
you will get an incorrect root which can cause certain things to load
incorrectly

Signed-off-by: David Maloney <DMaloney@rapid7.com>
Merge branch 'staging/electro-release' into bug/MSP-11050/rails_root
Land #3630, @wchen-r7's fix for datastore assignments on smb_enumusers
Land #3631, @wchen-r7's fixes to avoid datastore options assignment at runtime
Land #3642 - Be sure which the full payload is used
Add the check for the manual payload setting
Minor description adjustment
Dont fail_with while checking
Some style fixes
There is only one target
Merge to update