Better subcommand naming

[coryodaniel]

Now that we are starting to expose some of the other graph functions, particularly package functions like deploy... our commands are a bit confusing.

• mass app new makes a application bundle (source code)
• mass app publish publishes the bundle to our package manager
• mass deploy -> doesn't feel right as a top-level command since it technically 'deploys a package'...
• mass package deploy starts to sound really confusing wrt to package management (these are deployed resources), as would mass package configure

Since applications and bundles don't really have any differences in how they are execute, I propose we move them into just bundles subcommand. The only difference in how we managed the bundles is how they are templatized.

• mass bundle new - will make a new bundle from a template
  • our terraform template will need to move to application-templates (we should also rename this to bundle-templates)
  • terraform template will need to be updated to support liquid
• mass bundle publish - will publish a bundle (mind you "bundle" is becoming our generic term for a bag of IaC, current "bundle" types are going to be changed to "infra" or "infrastructure"

This will free up mass app to deal w/ end user applications:

mass app deploy ecomm-staging-api will deploy the application package mass app config ecomm-staging-api -f ./params.json would read JSON from file and configure the package for deployment

[WillBeebe]

"terraform template will need to be updated to support liquid" => already done, I grabbed this as part of the app templating

[WillBeebe]

I like mass app deploy and mass app config, and it makes sense to consolidate on bundle now. 👍