Move PyConf to LHCb to make accessible to other projects

A number of good reasons exist to move PyConf from Moore to LHCb, to allow usage of the new configuration framework in projects outside Moore.

The following discussion from !305 (merged) should be addressed:

• @apearce started a discussion: (+8 comments)

  On your last paragraph in the description about moving this back to Rec, is this something that's also useful to have for the track and CALO reconstruction @sstahl @mstahl @graven?

  If not, why is the RICH reconstruction special in this regard @jonrob? (Not arguing against it, just genuinely curious!)

See also for instance Rec!1795 (merged) !307 (merged)