Ensure WAITING state is set on resubmissions

[berland]

Upon resubmissions, this state did not get set, as it before was only set in init, with the result that the GUI showed wrong state (RUNNING) before the realization was submitted.

Issue Resolves #8079

Approach 📯

Screenshot shows that the realizations that failed in the first run are reset to Waiting (blue border):

• [x] PR title captures the intent of the changes, and is fitting for release notes.
• [x] Added appropriate release note label
• [x] Commit history is consistent and clean, in line with the contribution guidelines.
• [ ] Make sure tests pass locally (after every commit!)

When applicable

• [ ] When there are user facing changes: Updated documentation
• [ ] New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• [ ] Large PR: Prepare changes in small commits for more convenient review
• [ ] Bug fix: Add regression test for the bug
• [ ] Bug fix: Create Backport PR to latest release

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 86.02%. Comparing base (b803b91) to head (8ebc010).

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #8104 +/- ## ========================================== - Coverage 86.06% 86.02% -0.04% ========================================== Files 382 382 Lines 23714 23715 +1 Branches 626 618 -8 ========================================== - Hits 20410 20402 -8 - Misses 3231 3232 +1 - Partials 73 81 +8 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.