LDD Bug - State Transitions

**Describe the bug in current situation**
While testing a scenario around entering actuals, and moving a request from CFR to Records Review, and then moving from records review back to CFR, a strange behaviour was observed impacting the LDD.

Moving from records review back to CFR appears to credit a day back to the LDD

**Link bug to the User Story**

**Impact of this bug**
Describe the impact, i.e. what the impact is, and number of users impacted.

**Chance of Occurring (high/medium/low/very low)**
Medium - this will occur only if the state moves back to CFR. This could be possible if changes needed to be made to CFR actuals

**Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?**

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to a general request and go through the fee estimate flow
2. After paying deposit or full fee, enter actuals and move state to records review
3. Change state back to Call For Records
4. Days remaining will tick up by 1 day
5. This can be repeated to continually add additional days, each time the request is moved back to CFR

**Actual/ observed behaviour/ results**

**Expected behaviour**
GIVEN a request is in the records review state
WHEN the state is changed back to Call for Records
THEN the state will update to Call for Records
AND the legislated due date will remain the same

**Screenshots/ Visual Reference/ Source**
If applicable, add screenshots to help explain your problem. You an use screengrab.

Start by reproducing the fee estimate flow for a general request: enter actuals, move from Records Review to Call for Records, and observe the legislated due date and days remaining. Trace the state-transition handling for this path. Done means returning to Call for Records leaves the legislated due date unchanged and repeated transitions do not add days.

Written by the indexing model from the issue text.