Associate runtime images with runtime languages

[ptitzler]

Is your feature request related to a problem? Please describe. Currently the UI always displays all runtime images if a user needs to make a selection, e.g.

With the added support for R scripts not every image will support every language. We should consider

• Adding an optional property to runtime image metadata, which indicates what programming language runtime environment(s) it support. For example, the R Script image would indicate that it can only be used to run R code. (I realize that every runtime image also has Python installed to accomodate the bootstrapper, but that is a side effect, not a feature).
• If specified, use the property to filter out those runtimes that do not support the file type for which the user chooses the runtime image.

Example:

• (1) See screen capture above. The user has an R script open in the editor and wants to submit it for remote execution. Current behavior: all runtime images are displayed; new behavior: only the R script runtime image is displayed, because it's the only one that can process this type of file
• (2) Not depicted: Node properties would operate the same way because at the time when the user makes a selection the file type is known.

Describe the solution you'd like See above.

[kevin-bates]

The new metadata property should be multi-valued (list) since a given image could support multiple languages. Since we allow dynamic languages within Code Snippets, it should probably not be an enumeration.