refactor the internal logic of podGroupManager

[googs1025]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

• refactor the internal logic of podGroupManager

Which issue(s) this PR fixes:

Fixes #None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: googs1025
Once this PR has been reviewed and has the lgtm label, please assign huang-wei for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-scheduler-plugins canceled.

Name	Link
🔨 Latest commit	f66b53f
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-scheduler-plugins/deploys/67b68507a10a8c000842ac27

[googs1025]

I understand whether I need to call pgMgr.Reserve() in Reserve instead of creating the informer in NewPodGroupManager 🤔

[googs1025]

func (cs *Coscheduling) Reserve(ctx context.Context, state *framework.CycleState, pod *v1.Pod, nodeName string) *framework.Status {
	return nil
}

[googs1025]

@ffromani @Huang-Wei
can you help this ? :)

[ffromani]

thanks for the PR! what's the goal here? "refactor the internal logic of podGroupManager" seems a bit too generic :) Is this about contextual logging (I see context being passed around) or what?

[k8s-ci-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.