Updating an easystack file for a new toolchain

There is support for running `--try-*` options against an easystack file, and this can be used to build for a newer toolchain (for example).

However, it would be useful if a new easystack file could be rendered with all the amended easyconfigs listed in it.

That way, the benefit of a single file specifying the complete module tree installation is retained.