Support for actions and plugin commands aliases

[davidferlay]

Current

• Action commands can be executed by calling name defined in action.yaml title
• Plugin commands can be executed by calling name defined in plugin.go Use
• In either case, one command can only be called by one name: same command cannot have multiple names

Expected

• It would be great to have ability to define additional names to execute commands (aliases)
• Developer creating a plugin or an action would define a list of aliases

[davidferlay]

#44

Working fine 👌

➜ ./plasmactl platform:nodes --help   
Nodes: Get nodes from online.net and generate cache file

Usage:
  plasmactl platform:nodes [flags]

Aliases:
  platform:nodes, deployalias

Flags:
      --clusters string   clusters: The server hostname filter
  -h, --help              help for platform:nodes
      --no-cache          No cache: Send command to build container without cache
      --remove-image      Remove Image: Remove an image after execution of action
      --servers string    servers: The servers list to get info for (overrides servers from configs)
      --use-volume-wd     Use volume as a WD: Copy the working directory to a container volume and not bind local paths. Usually used with remote environments.

Global Flags:
      --keyring-passphrase string   Passphrase for keyring encryption/decryption
  -q, --quiet                       disable stdOut
  -v, --verbose count               log verbosity level, use -vvv DEBUG, -vv WARN, -v INFO

➜ ./plasmactl platform:nodes       
Image "platform-actions-nodes:latest" exists locally
Proceeding with execution, please wait...
Successfully created cache in library/inventories/platform_nodes
➜ ./plasmactl deployalias          
Image "platform-actions-nodes:latest" exists locally
Proceeding with execution, please wait...
Successfully created cache in library/inventories/platform_nodes