Base Year not reported if it is one of the Years run in a future scenario

[jrawbits]

VisionEval 3.x has a couple of places where it is presumed that the BaseYear is a stage unto itself. Some older models are most easily set up to make the BaseYear just one of the years within a particular scenario. The main problem with such a setup is that the BaseYear is not exported because VisionEval doesn't want to make multiple copies of it in each scenario.

To avoid the problem in the first place, make the BaseYear its own stage and use the "StartFrom: BaseYearStage" instruction for each future stage or scenario in visioneval.cnf.

To save people from themselves (at the expense of possibly running and reporting multiple copies of the base year if peopl ehave included it to run in multiple stages), obtaining results should include the BaseYear if it is present in Datastore at the top of DatastorePath, but not if the BaseYear is further down the DatastorePath.