Right now we wrap ray.init inside fed.init, whch means fed.init handles the init of ray and fed, maybe we should
move ray.init out of fed.init, benifits:
Cleaner user facing apis: user explictly calls ray.init and fed.init, decouple fed.init from ray.init
Works better with other ray-eco libraries which both require ray.init, for example RayDP
Right now we wrap
ray.initinsidefed.init, whch meansfed.inithandles the init of ray and fed, maybe we should moveray.initout offed.init, benifits:ray.initandfed.init, decouplefed.initfromray.initray.init, for example RayDP