Vagrant build steps like 'Provision' and 'Execute ssh' should allow for the use of environment variable references to make jobs that use them more useful (like in a matrix build environment that uses a single vagrant file for many machines).

Currently, all fields are interpreted at face value - $WORKSPACE does not get expanded, which is particularly problematic when combined with https://issues.jenkins-ci.org/browse/JENKINS-26326