SelectRecoMC doesn't run on non-MC data

[brownd1978]

Our workflows depend on SelectRecoMC, which creates output data collections of subsets of low-level objects associated with reconstructed (and MC-matched) objects. Many workflows explicitly and implicitly rely on it.
We need to generalize this module to perform a similar task on data without MC. It requires a new module, as we don't want to have to link against MC codes when running reconstruction on non-MC data.
I clean solution is to use SelectReco as an instance name, and have different modules behind it depending on whether the job is processing MC or non-MC data. The output payload would be structually the same. This will be disruptive to downstream consumers as the name SelectRecoMC appears in multiple repositories.