When you set a stage variable, it automatically passes that down as an environment variable to all steps within that stage, even through templates, etc. This is disastrous for pipeline clarity and modularity because it's impossible to tell which stage vars are used for which steps and references to environment variables deep inside the code of a template might be relying on a stage-level variable at the pipeline level and there's no way to track that. Please provide a way to turn this off and only pass stage variables down to the environment variable level if they are specifically referenced using the envVariables system.
