Traditionally, matrix axis values are only exposed as "build variables", and it was up to individual build steps and others to treat them equally like environment variables.

However, in practice, this distinction between environment variables vs build variables didn't serve any useful purposes, and the down side (of some plugins only expanding env vars in the ${VAR} notation and not build variables) was probably bigger than whatever benefit this distinction was supposed to bring.

In this fix, we are exposing matrix axis values also as environment variables. This will make them recognizable from plugins that only expand environment variables, such as parameterized trigger plugins as indicated in the original bug report.

This was motivated by pull request #701 but fix was made differently.

Introduced ${ITEM_FULL_NAME} to address the ticket without causing the
backward compatibility problem.

This is done by introducing a new base type 'BuildDiscarder' that's
extensible. Plugins can implement their own logics.

This reverts commit e2168722.

Fixed the HTTP request thread saturation problem with Winstone.

eval("") is no-op in IE but window.execScript("") isn't.
So bring the uniformity outside

This was lost in 0f2737f8

While several plugins implemented the interface under the old name, only core was checkcasting it.

At this time the target project is unset so it has no known type and we just have to assume the threshold is valid.

First, display instructions when the user has CONNECT, not necessarily ADMINISTER.
Second, when anonymous users cannot CONNECT, show how to use -jnlpCredentials
(and do not bother showing javaws, since it does not work in this case).