Add command-line switch for detect deployment type

[TrueWill]

Specifying -d or --detect-deploy on the command line will cause mulint to detect the deployment type (on-prem or CloudHub). This is the current behavior. Omitting that means that mulint will assume on-prem deployment.

[UKachegere]

@TrueWill
I am not sure -d option is the right way to go if you would like this to work it for any deployment type ie on-prem or cloud. Making an assumption that it is on-prem might work for UFG's setup. It might not work for companies having all cloudhub deployments.

Would throwing error and stop processing when "mule-maven-plugin" is present and any deployment information is not in the pom file? If we are using Anypoint CLI and not using Maven plugin to deploy, none of those information should be in the POM file and needs to be removed.

Hope this make sense. Let me know if you have questions

[TrueWill]

@UKachegere My thought was that UFG would run mulint without the switch, so it would default to on-prem. Other companies could run mulint with the switch, and it would look at the deployment.type in the POM. Alternately they could open a PR to add a --cloudhub switch that would default to CloudHub.

We can either error (fatal) or warn on any condition you like. I just need to know what the conditions are and the severity.

[TrueWill]

@UKachegere Please let me know if you'd like me to close this PR.