[Colocation Enhancement] Support configurable node monitor parameters

[JesseStutler]

What is the problem you're trying to solve

Currently, in volcano colocation scenario, When the usage of a resource exceeds a threshold (such as CPU), six consecutive instances of exceeding the threshold (detected every 10 seconds) are required before eviction of BE pods. Currently, this is hard-coded, we need to make it configurable for users.

The highUsageCountLimit constant is currently hardcoded:
https://github.com/volcano-sh/volcano/blob/7b14346ab7a7c46814da3951a21ee3cad9ccf5c0/pkg/agent/events/probes/nodemonitor/node_monitor.go#L201C47-L201C66
as are the frequencies of detect and monitor:

volcano/pkg/agent/events/probes/nodemonitor/node_monitor.go

Lines 87 to 88 in 7b14346

	go wait.Until(m.utilizationMonitoring, 10*time.Second, stop)
	go wait.Until(m.detect, 10*time.Second, stop)

).

Describe the solution you'd like

We need to support configurable values, we can still set 10 seconds and 6 times for highUsageLimit by default

Additional context

No response

Documentation Updates

• This feature requires design or user documentation changes.
• If documentation changes are required, I will ensure the relevant documents are updated and published to the Volcano official website (https://volcano.sh) via the volcano-sh/website repository.

[JesseStutler]

/good-first-issue

[volcano-sh-bot]

@JesseStutler:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

Details

In response to this:

/good-first-issue

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/test-infra repository.

[JesseStutler]

/area colocation

[kajal-jotwani]

/assign

[AmanKumar1411]

/assign