Pipelines that name a step as `in` (e.g. `input('exposures') as in`) will now produce
an error.  The `in` step name has special meaning and can only used as a step reference
to denote the starting point of a sub-pipeline.
