Fix inconsistencies between old and run3-style configuration

• the name of some SCT_DCSConditions algorithms was different in the old and run3-style configuration which may lead to conflicts when using old and run3-style configuration snippets in the same job i.e. two "different" algorithms would try to write the same conditions data
• In the old configuration the Pixel DCSCondState and PixelDCSCondStatus algorithm was not setting the ReadCondHandleKey for data jobs. The keys are empty by default, thus the corresponding DCS information was never read from the database. However the key was set in the run3-style configuration for data. This fix may lead to some differences when processing data since this conditions data was not used but would be used now and may flag some pixel modules to be bad now.