module map ES producers

[slava77]

this is a concept PR at this point: I start with making ES products for module maps in the host space.
For a start it seemed easier to convert just one module map load.
Since most other maps are the same and are independent they could as well be populated with the same ES producer clones.

To run this one also needs a data area known to CMSSW :

dataD=$CMSSW_BASE/external/$SCRAM_ARCH/data/RecoTracker/LST
mkdir -p $dataD
cd $dataD
ln -s $LST_BASE/data

Ultimately, it would be good to create and fill data (almost) directly usable by modulesBuf->moduleMap_buf and nConnectedModules_buf as ES products in the device space.

[slava77]

I filled the PR description with smth more readable for the plan

[VourMa]

The ESProducer will need to be moved under the alpaka/ directory and migrate to the alpaka format, before this can be merged. A discussion is needed whether such a development makes sense given that @slava77 is working already on a similar but different implementation for that.

[VourMa]

Should we close this? I guess it is superseded by PR #16?