Add workflows for RasterAnalytics and ImageHosting roles to arcgis-server-linux template

Template arcgis-server-linux supports federating the ArcGIS Server site in RasterAnalytics and ImageHosting roles (a.k.a. server functions), but does not provide ready-to-use workflows and config files for these roles.

The "workflows" directory of arcgis-server-linux template should include workflows for each supported server role:

```text
arcgis-server-linux/
...
workflows/
gis-server/
gis-server-linux-aws-application.yaml
...
image-hosting/
image-hosting-linux-aws-application.yaml
...
raster-analytics/
raster-analytics-linux-aws-application.yaml
...
server/
server-linux-aws-application.yaml
...
```

> The only differences between the workflows for the roles will be the path to the workflow config files.

And the "config" directory of the repository should include config files for the workflows:

```text
config/
aws/
...
arcgis-gis-server-linux/
application.tfvars.json
...
arcgis-image-hosting-server-linux/
applocation.tfvars.json
...
arcgis-raster-analytics-server-linux/
application.tfvars.json
...
arcgis-server-linux/ (Standalone ArcGIS Server)
application.tfvars.json
...
```

The config files should provide appropriate default values for the server roles, in particular:

- "deployment_id" property values must be different for different roles ("server-linux" for standalone ArcGIS Server, "gis-server-linux" for GIS Server, "image-hosting-server-linux" for Image Hosting Server, and "raster-analytics-server" for Raster Analytics Server).
- "server_web_context" property values in image.vars.json files must be different ("arcgis" for standalone ArcGIS Server and GIS Server, "image" for Image Hosting Server, and "raster" for Raster Analytics Server).
- "instance_type" and "root_volume_*" property values in infrastructure.tfvars.json files should match the system requirements of the server roles.
- "server_role" and "server_functions" property values in in application.tfvars.json files should be set based on the server roles.
- "server_authorization_file_path" property values in application.tfvars.json files should have different placeholder values (for example "~/config/authorization/12.0/image_hosting_server_120.prvc").

> Support for Knowledge Server role should be addressed in a separate issue.