Mark status tests for testing with Scheduler

[berland]

These are currently skipped

Issue
Resolves part of #6810

Pre review checklist

• Read through the code changes carefully after finishing work
• Make sure tests pass locally (after every commit!)
• Prepare changes in small commits for more convenient review (optional)
• PR title captures the intent of the changes, and is fitting for release notes.
• Updated documentation
• Ensured that unit tests are added for all new behavior (See
  Ground Rules),
  and changes to existing code have good test coverage.

Pre merge checklist

• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e4230ff) 83.88% compared to head (9416c09) 83.86%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6819      +/-   ##
==========================================
- Coverage   83.88%   83.86%   -0.02%     
==========================================
  Files         365      365              
  Lines       21383    21383              
  Branches      948      948              
==========================================
- Hits        17937    17933       -4     
- Misses       3152     3156       +4     
  Partials      294      294              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jonathan-eq]

There is a minor typo in commit message Mark status tests for testing with cheduler.

Also, it seems like most of those tests are integration tests and not unit tests, so they might have already been moved (and had the fixtures added) in a unmerged/blocked PR #6787
Should I rebase the other PR?

[berland]

Fixed typo. If 6787 is merged, I will rebase this.

[jonathan-eq]

LGTM!