Include support for CLI API for actions currently performed via HTTP API

[EmersonPrado]

Custom resource wildfly_cli nicely executes JBossCLI/WildFly commands thru an HTTP connection to JBoss/WildFly server. But, in case we need to change any configuration before starting the server, we need to resort to the embedded server.

My proposal is to either write a new provider "embedded" to the existing type wildfly_cli. I managed something in a module used internally at work, but I think this would better suit this public module.

[EmersonPrado]

Some basic facts require a big change:

• Main entry point for general Wildfly resource changes is defined type wildfly::resource, which uses custom resource wildfly_resource
• Moving from HTTP API to embedded server is, actually, a two-step process
  • Implement CLI API
  • Implement embedded server

So, I'm changing this issue to implement CLI API support, maybe as a common provider or shared library, which could serve wildfly_cli and wildfly_resource. And leaving the embedded server part for a future issue.

[EmersonPrado]

Proposal for code organization:

• Provider wildfly_cli::cli_api
  • Validate CLI commands from command parameter
  • Validate results
• Provider wildfly_resource::cli_api
  • Check current resource state
  • Format CLI commands from state parameter
  • Validate results
• Base provider cli_api
  • Coordinate methods and data
• Utility Ruby modules
  • Run API
  • Connect and authenticate to Wildfly server
  • Run commands
  • Format results as a Ruby hash