feat(updater): support manually specifying priority

[liubog2008]

• support specifying priority for scale in and update

[codecov-commenter]

Codecov Report

❌ Patch coverage is 95.23810% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 39.36%. Comparing base (de4330b) to head (b0c2da6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6641      +/-   ##
==========================================
+ Coverage   39.28%   39.36%   +0.08%     
==========================================
  Files         351      351              
  Lines       20692    20676      -16     
==========================================
+ Hits         8129     8140      +11     
+ Misses      12563    12536      -27     

Flag	Coverage Δ
unittest	39.36% <95.23%> (+0.08%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: srstack

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [srstack]

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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-01-06 10:57:39.820744563 +0000 UTC m=+699815.639052985: ☑️ agreed by srstack.

[liubog2008]

/test pull-e2e

[ti-chi-bot]

@liubog2008: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-e2e	b0c2da6	link	unknown	/test pull-e2e

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.