[Feature] Support for Component Priority Class Configuration in Karmada Operator

[RainbowMango]

Background
Currently, the priority class name for Karmada components is hardcoded to system-node-critical for some components, while others do not specify a priority class at all. This limitation can compromise the reliability and stability of the system in environments where scheduling of critical components is essential.

Proposal

• Proposal: Add Support for Component Priority Class Configuration in Karmada Operator #6010 (@jabellard)

Author:

• @jabellard

Iteration Tasks

• Feature implementation (@jabellard)
• Unify the PriorityClass configuration(defaults to system-node-critical) in helm chart
• Unify the PriorityClass configuration(defaults to system-node-critical) in karmadactl init
• Unify the PriorityClass configuration(defaults to system-node-critical) in karmadactl addon
• Unify the PriorityClass configuration(defaults to system-node-critical) in hack/local-up-karmada.sh
• Feature documentation
• TBD(How to cover this feature in CI test suite?)