Make gRPC APIs and config functionalities of web UI aligned

[hm2501]

Feature request:

Currently dragonfly manager provides gRPC APIs for various operations. But some operations (e.g. managing clusters, schedulers, etc) are only possible on the web UI. It's great if all operations can be done on gRPC APIs for making automation easier.

Use case:

Implementing k8s operator for dragonfly will be easier.

UI Example:

n/a

[FillZpp]

especially for some configuration like peer load limit

[FillZpp]

thanks @gaius-qi

[CooooolFrog]

Do you want to call some existing gRPC interfaces of Manager through the Golang SDK?

type ManagerClient interface {
	// Get SeedPeer and SeedPeer cluster configuration.
	GetSeedPeer(ctx context.Context, in *GetSeedPeerRequest, opts ...grpc.CallOption) (*SeedPeer, error)
	// List acitve schedulers configuration.
	ListSeedPeers(ctx context.Context, in *ListSeedPeersRequest, opts ...grpc.CallOption) (*ListSeedPeersResponse, error)
	// Update SeedPeer configuration.
	UpdateSeedPeer(ctx context.Context, in *UpdateSeedPeerRequest, opts ...grpc.CallOption) (*SeedPeer, error)
	// Delete SeedPeer configuration.
	DeleteSeedPeer(ctx context.Context, in *DeleteSeedPeerRequest, opts ...grpc.CallOption) (*emptypb.Empty, error)
	// Get Scheduler and Scheduler cluster configuration.
	GetScheduler(ctx context.Context, in *GetSchedulerRequest, opts ...grpc.CallOption) (*Scheduler, error)
	// Update scheduler configuration.
	UpdateScheduler(ctx context.Context, in *UpdateSchedulerRequest, opts ...grpc.CallOption) (*Scheduler, error)
	// List acitve schedulers configuration.
	ListSchedulers(ctx context.Context, in *ListSchedulersRequest, opts ...grpc.CallOption) (*ListSchedulersResponse, error)
	// List applications configuration.
	ListApplications(ctx context.Context, in *ListApplicationsRequest, opts ...grpc.CallOption) (*ListApplicationsResponse, error)
	// KeepAlive with manager.
	KeepAlive(ctx context.Context, opts ...grpc.CallOption) (Manager_KeepAliveClient, error)
}

The configuration of the peer load limit mentioned here should be implemented through the UpdateScheduler gRPC interface.

I will try to complete this requirement, and I will synchronize any progress in this issue.