Add pprof for karmada components

[Poor12]

Signed-off-by: Poor12 shentiecheng@huawei.com

What type of PR is this?
/kind feature

What this PR does / why we need it:
Since we need to do some performance tests for karmada components, we found that there are still some components which do not support pprof.

Because each components have different implementing logic, some are based on genericAPIServer, some are base on controller-runtime(controller-runtime now do not support pprof kubernetes-sigs/controller-runtime#1943). In this PR, we unify the config to enable pprof.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:
Karmada-agent, Karmada-aggregated-apiserver, Karmada-controller-manager, Karmada-descheduler, Karmada-search, Karmada-scheduler, Karmada-scheduler-estimator, Karmada-webhook now support --enable-pprof to enable pprof and --profiling-bind-address to config address for pprof web server.

[RainbowMango]

Please share the test reports and remember to cc the students who are doing the performance thing.

[Poor12]

1. First enable the flag.
   
2. Curl PodIP to get pprof file.
   

[RainbowMango]

@lonelyCZ Can you help to take a look?

I'm thinking if we need to introduce the shared flags, just like what we did at klog-flag.

[lonelyCZ]

I'm thinking if we need to introduce the shared flags, just like what we did at klog-flag.

I think it is a good idea. These flags apply to karmada-agent and karmada-controller-manager. Such as pkg/sharedcli/pprofflag/pprofflag.go

[RainbowMango]

Maybe the reason why karmada-schedule enabled pprof is:

• imports k8s.io/apiserver/pkg/server at here -->
• k8s.io/apiserver/pkg/server imports k8s.io/apiserver/pkg/server/routes at here
• k8s.io/apiserver/pkg/server/routes imports net/http/pprof at here

And finally, karmada-scheduler starts the http-server.

@Poor12
Please confirm.
If we are going to introduce flags for profiling, we should ensure the profiling feature could be disabled.
So, I think we need another PR before this.

By the way, the similar issue happens at karmada-descheduler.

[lonelyCZ]

/assign

[RainbowMango]

Generally looks good to me.

[RainbowMango]

/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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 [RainbowMango]

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

[RainbowMango]

Please describe how to grab the pprof data from Karmada build by hack/karmada-local-up.sh.

[Poor12]

cc @lonelyCZ to review. For further usage, you can base on #2141

[lonelyCZ]

I just tested it that worked fine. Thanks~

/lgtm