distinguish specification from recipe

[fosterlynn]

Discussion in the HoloREA project related to modularizing the VF software led to this thought. Do we want to split out the ResourceSpecification from the recipe? It will work without that, but it seems cleaner, mostly so that other modules can reference the ResourceSpecification without getting into the needs of the recipe.

It could look like this:

(Need better name for resourceRecipe property. And am not totally sure about property split.)

(Similar issue possibly exists for RecipeProcess but it is not totally the same. I think it could be better addressed when we get workflow recipes defined, where the same resource is input and output of a series of processes.)

cc @pospi @sqykly

[fosterlynn]

From more work on HoloREA modularization, I think we should do process in the same way. Also some clarification from @bhaugen on what properties might be needed in ResourceSpecification aside from recipe. Looks like this atm:

[fosterlynn]

Done.