CFR Actuals - Field Locked Harms Assessment

**Describe the bug in current situation**
User report indicated that they were not able to update the fee estimate actuals on a request while the state was in harms assessment

**Link bug to the User Story**
#2198

**Note - the original story does not specify that a request must be in the CFR state to enter actuals, but that is how the app behaves.

**Impact of this bug**
Mild - there is a workaround where a user can move a request from harms to CFR to enter the actuals if they find themselves in this situation.

**Chance of Occurring (high/medium/low/very low)**
High - when the conditions occur, this is easily replicable.

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

**Steps to Reproduce**
Steps to reproduce the behavior:
1. Go to a request with a paid estimate in CFR
2. Change state to Harms assessment
3. Go to CFR Form
4. Fields are unable to be edited

**Actual/ observed behaviour/ results**

**Expected behaviour**
A clear and concise description of what you expected to happen. Use the gherking language.

* GIVEN a FOI request has any amount of a fee estimate recorded as paid
* WHEN a Ministry coordinator navigates to the fee estimate page
* THEN the fields for actual hours and volume of pgs will be editable
* AND the fields for the original estimate will be greyed out and uneditable

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

Start by reproducing the issue from a request with a paid estimate: change its state from CFR to Harms assessment, open the CFR Form, and inspect the actual-hours and volume-of-pages fields. Done means those actuals remain editable in Harms assessment while the original estimate fields remain greyed out, as described by the GIVEN/WHEN/THEN criteria.

Written by the indexing model from the issue text.