Redefine the FightManifest specification

[ColonelPanicks]

Allow "descriptions" for deployments. This information could come from multiple places:

• Metadata description key for the deployment
• Description tag from deployment
• Description key for group (I'm aware there isn't group-specific stuff in cloud yet so this might need some scoping)
• Description from instance type (if using maps for #248 then it should be fairly easy to add some additional instance type data)

The idea of this is so that nodes can print various human-readable information that'll be especially useful to end-users that are looking at nodes via Flight Cloud Client. For example:

Deployment: ‘gateway1’
-----------------------------------------------------------------
Description: The login node for the cluster, SSH into this system to be able to run jobs.
Creation Date: 2019-07-24 15:47:40 +0100
Status: Running
Provider Tag: cloudware-shared-gateway1-ce9b3f3cd7
Groups: login,login,all

  Results
  ● gateway1TAGgroups: login,all
  ● gateway1TAGIP: 3.248.88.42
  ● gateway1TAGID: i-021d5339da4ba5d93

  Replacements
  ● deployment_name: gateway1
  ● securitygroup: *domain
  ● network1SubnetID: *domain
  ● network2SubnetID: *domain

Potentially the description would concatenate all applicable descriptions for the deployment into one description line.

[WilliamMcCumstie]

In addition to the above issue the current version of FlightManifest only allows for certain fields to be included in the export. Instead the manifest should be able to specify the following at any level:

name:
description:
parameters: # => Hash of arbitrary key value pairs. Should be imported as Replacements
files: # => A key value hash of file type and path. The `aws` and `azure` keys should be used

At the node level, the following keys should be added:

other_groups:
primary_group: