feat: ash_cli module

[leopaul36]

Linked issues

• Fix Implement an Ash CLI module #62

Changes

• Add ash.avalanche.ash_cli Ansible module

Additional comments

There is still room for improvements:

• The module is currently "stateless", it either return ok or fatal. We could return changed once we merge the transaction feature to Ash CLI.
• We could also parse the command to see if it's part of an allowed list but I'm not sure we want to do this for maintainability.

[leopaul36]

Docs PR: AshAvalanche/ash-docs#42

[Nuttymoon]

A few remarks:

• A role named ash_cli already exists. What about ash_cmd or ash_command for the module name? (can be both with a symlink)
• I would appreciate having the command run as a string in the output. E.g. command: /usr/local/bin/ash avalanche node info
• We should handle positional arguments: maybe with a positionals module argument

  positionals=dict(type="list", required=False, default=[]),

[Nuttymoon]

Note that the module actually already supports positionals if we pass them in the command argument. Yet I don't really like this option as it makes it quite unreadable with multiple positionals. (Anyway people can still do as they please even if we add positionals)

[leopaul36]

A few remarks:

* A role named `ash_cli` already exists. What about `ash_cmd` or `ash_command` for the module name? (can be both with a symlink)

* I would appreciate having the command run as a string in the output. E.g. `command: /usr/local/bin/ash avalanche node info`

* We should handle positional arguments: maybe with a `positionals` module argument
  ```python
  positionals=dict(type="list", required=False, default=[]),
  ```

• command can now accept a list of strings (or just a single string which will be parsed as a one item list)
• Module has been renamed from ash_cli to ash_cmd
• command is passed in the output on both failure and success