Coscheduling: Remove the postBind filter in the KubeSchedulerConfiguration

[tenzen-y]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

I removed the PostBind filter in the KubeSchedulerConfiguration because the PostBind filter was removed in the #554.

Which issue(s) this PR fixes:

Fixes #

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	7957ac0
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-scheduler-plugins/deploys/6558232f1997d800076f1bf5

[tenzen-y]

I think that it would be better to cherry-pick this to the release-0.26 and release-0.27 branches.

[Huang-Wei]

I think that it would be better to cherry-pick this to the release-0.26 and release-0.27 branches.

Actually specifying a non-existent extension point would fail scheduler's startup. But yes, let's fix the documents. And, we should turn to using MultiPoint to simplify the scheduler config.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

[tenzen-y]

I think that it would be better to cherry-pick this to the release-0.26 and release-0.27 branches.

Actually specifying a non-existent extension point would fail scheduler's startup. But yes, let's fix the documents. And, we should turn to using MultiPoint to simplify the scheduler config.

/lgtm /approve

That makes sense.

[tenzen-y]

/cherry-pick release-0.26