Refactor environment name by removing it from resource name and adding it as a tag instead

[eistrati]

In order to enable deepify to push different environments from one stage into another (e.g. stage push into prod, or prod to rollback into stage), we need to remove environment name (e.g. dev, test, stage, prod) from resource names (e.g. DeepDevLambdaExecution1234abcd, DeepStagePropertyRetrieve5678wxyz) and add instead tags for new environments or update tags for existing ones (e.g. DeepDevLambdaExecution1234abcd will become DeepLambdaExecution1234abcd with tag DeepEnvironment=dev, DeepStagePropertyRetrieve5678wxyz will become DeepPropertyRetrieve5678wxyz with tag DeepEnvironment=stage)

[mgoria]

After analysing current resource naming implementation and other deep ecosystem related implementations I see some impediments here:

1. Removing env name from resource name will result into naming collisions with other deployed apps.
2. Not all services support Tagging.
3. In order to enable deepify to push different environments from one stage into another we have to redeploy the app with parameters for this specific environment (e.g. In dev we use some stripe keys in prod we have different ones)