refactor: enhance logging and error handling in scheduler functions

[haitwang-cloud]

What type of PR is this?
/kind flake

What this PR does / why we need it:

This PR mainly optimizes and standardizes the logging in scheduler.go:

Unifies and adjusts log levels for better readability.
Adds structured logs with more details (such as pod, node, and device information).
Improves error log context to make troubleshooting easier.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:
No

[hami-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: haitwang-cloud
Once this PR has been reviewed and has the lgtm label, please assign archlitchi for approval. 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:

• OWNERS

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

[codecov]

Codecov Report

Attention: Patch coverage is 50.76923% with 32 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
pkg/scheduler/scheduler.go	50.76%	32 Missing ⚠️

Flag	Coverage Δ
unittests	54.08% <50.76%> (+1.06%)	⬆️

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

Files with missing lines	Coverage Δ
pkg/scheduler/scheduler.go	50.46% <50.76%> (+4.55%)	⬆️

... and 5 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[haitwang-cloud]

@chaunceyjiang @lengrongfu @archlitchi @wawa0210 PTAL,tks

[lengrongfu]

We can use 4 level.

[haitwang-cloud]

@lengrongfu Addressed your comment, PTAL again