Blueprints: allow for expansion of env value fields

[goosenation]

Some env fields can hold a lot of data. An example of such data is the PLUGINS key in this screenshot. It accepts a comma-separated string of plugins, and the list can get very long.

My current workaround is to copy/paste the contents of the field in an ide or text editor, and review/edit it in there, then pasting it back.

I understand that this is only one field in a long list of fields, and having a textarea for all of these fields would not be beneficial.

But perhaps there is a way to improve the experience?

[mvaessen]

Thanks for the suggestion! This has been added