fix(QOSSort): refine queue sorting logic by adding inqueue timestamp

[googs1025]

What type of PR is this?

/kind bug

What this PR does / why we need it:

• After comparing with the k/k queuesort package, we seem to be missing timestamp comparison.
  https://github.com/kubernetes/kubernetes/blob/35d6959ace07a4edc2a17da3bd4d0fcd625caa83/pkg/scheduler/framework/plugins/queuesort/priority_sort.go#L40-L49

Which issue(s) this PR fixes:

Fixes #None

Special notes for your reviewer:

Does this PR introduce a user-facing change?

None

[netlify]

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

Name	Link
🔨 Latest commit	3b77d02
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-scheduler-plugins/deploys/6785b671c839d70008dd65c5

[googs1025]

friendly ping @Huang-Wei

[googs1025]

There seems to be some unstable flakes here, I still need to think about how to deal with it. 🤔

[googs1025]

/test pull-scheduler-plugins-integration-test-master

[Huang-Wei]

@googs1025 this plugin was created just for demonstration purpose, and not enabled by default (if not in any case):

scheduler-plugins/cmd/scheduler/main.go

Lines 63 to 66 in 1e1b6b0

	// Sample plugins below.
	// app.WithPlugin(crossnodepreemption.Name, crossnodepreemption.New),
	app.WithPlugin(podstate.Name, podstate.New),
	app.WithPlugin(qos.Name, qos.New),

So it's not required to "sync" with the upstream plugin.

[googs1025]

@googs1025 this plugin was created just for demonstration purpose, and not enabled by default (if not in any case):

scheduler-plugins/cmd/scheduler/main.go

Lines 63 to 66 in 1e1b6b0

	// Sample plugins below.
	// app.WithPlugin(crossnodepreemption.Name, crossnodepreemption.New),
	app.WithPlugin(podstate.Name, podstate.New),
	app.WithPlugin(qos.Name, qos.New),

So it's not required to "sync" with the upstream plugin.

This pr is not to sync k/k upstream code. We are currently using the qos plugin internally. When we used it, we found that the sorting seemed to be a bit missing. The original logic only considered priority and qos type. IIUC, this is not to sync with the upstream, but to complete the missing part.

[Huang-Wei]

We are currently using the qos plugin internally. When we used it, we found that the sorting seemed to be a bit missing.

ok, good to know that.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: googs1025, Huang-Wei

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Huang-Wei]

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