feature: Support multiple profiles

[daimaxiaxie]

What type of PR is this?

/kind feature

What this PR does / why we need it:

The cluster scheduler can use multiple profiles to perform different scheduling for different pods. However, the current Cluster Autoscaler only supports one profile, which will lead to inaccurate scale up and down.

Feature issue #6544

Special notes for your reviewer:

Does this PR introduce a user-facing change?

flag scheduler-config-file support the same configuration file as scheduler.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[towca]

/ok-to-test

[MaciekPytel]

Overall this looks good to me, modulo the backward compatibility aspect of failing on unknown scheduler names. @alculquicondor I wonder if you would mind doing a quick sanity check on changes in schedulerbased.go to see if there are any potential problems with initializing framework that way from CA? I don't see anything, but you have much more expertise here.

[alculquicondor]

Overall LGTM from scheduler perspective

[x13n]

/assign @MaciekPytel

Looks like you were reviewing this already, can you follow up? Is it ok to merge now?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: daimaxiaxie
Once this PR has been reviewed and has the lgtm label, please ask for approval from maciekpytel. For more information see the Kubernetes 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:

• cluster-autoscaler/OWNERS

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

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[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.