Actually marking steps as "Deprecated" has problems.
We still need to provide a way in generated documentation for steps and global variables to mark themselves as deprecated, what version of they were deprecated in, and provide helpful text about what a user can do about it.

This would lay the groundwork for making longer term Pipeline changes and improvements, that respect backward compatibility but are not prisoner to it.