Encapsulation of Trainer class

[joneswong]

In our design, Trainer class is responsible for encapsulating much training and testing details. Thus, we'd better make it clear: what interfaces are needed for Client class to interact with a trainer. IMO, directly accessing a trainer's property (e.g., context) should be forbidden:

FederatedScope/federatedscope/core/worker/client.py

Line 413 in bc6eb8b

self.trainer.ctx.num_train_batch

Only in this way can our users develop a trainer in their own ways, respecting these interfaces while totally ignoring our design of the base trainer.