koord-scheduler: strictly check whether ReservationInfo is available or terminating

[eahydra]

Ⅰ. Describe what this PR does

Users create reused Reservation with finalizer, when need to delete Reservation, users first mark Reservation deleting, and clean other resources, then finally remove the finalizer to release Reservation.

• If the ReservationInfo (both Reservation CRD object and operating Pod) is terminating, the ReservationInfo cannot be used.
• In assume stage, if the ReservationInfo in cache is terminating, the assume operation will be rejected.

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it

Ⅳ. Special notes for reviews

V. Checklist

• I have written necessary docs and comments
• I have added necessary unit tests and integration tests
• All checks passed in make test

[FillZpp]

/lgtm

[codecov]

Codecov Report

Patch coverage: 57.14% and project coverage change: +0.04 🎉

Comparison is base (db67e64) 64.65% compared to head (62b7c95) 64.69%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1354      +/-   ##
==========================================
+ Coverage   64.65%   64.69%   +0.04%     
==========================================
  Files         325      325              
  Lines       33678    33687       +9     
==========================================
+ Hits        21773    21795      +22     
+ Misses      10318    10298      -20     
- Partials     1587     1594       +7     

Flag	Coverage Δ
unittests	64.69% <57.14%> (+0.04%)	⬆️

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

Impacted Files	Coverage Δ
pkg/scheduler/plugins/reservation/plugin.go	79.93% <42.85%> (-1.16%)	⬇️
pkg/scheduler/plugins/reservation/cache.go	87.14% <50.00%> (-3.97%)	⬇️
pkg/scheduler/frameworkext/reservation_info.go	31.84% <100.00%> (+17.00%)	⬆️
pkg/scheduler/plugins/reservation/transformer.go	68.57% <100.00%> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[jasonliu747]

/lgtm

[FillZpp]

/lgtm

[koordinator-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: FillZpp, hormes, jasonliu747

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:

• pkg/scheduler/OWNERS [hormes]

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