Bug - New facilities cannot be added to a report where operation has been transferred away

#### Describe the Bug:
Operator A starts a report for Operation 1 (LFO). Operation 1 gets transferred to Operator B. Operator A resumes the report for Operation 1 and tries to add a new facility. The add new facility button directs to Administration and an internal service error is shown because Operator A does not have permission to change Administration data for Operation 1 anymore.

#### Probability:

(How likely the bug is to happen, scored from 1-5. For example, probability of 5 is something like "it happens to all users every time they log in." whereas probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")

#### Impact:

(How bad the bug is when it does happen, scored from 1-5. For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected." whereas effect of 1 is "It makes some styling look a little bit weird.")

#### Steps to reproduce the behaviour:

1. Identify an in-progress (draft/supplemental draft) report for an LFO Operation
2. As an internal user, transfer that operation to a new operator.
3. Login as an approved UserOperator for the original operator.
4. Resume the draft report and progress to the ```Review-Facilities``` page
5. Click the ```Add it here``` link to add a new facility
- See that you are shown an "Internal Server Error" page

#### Screenshots:

#### Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]

#### Additional Context

- This is not an easy fix, and will likely need to be addressed in wider work around how we deal with new data in reports involving transferred entities and past years.

Start at the Review-Facilities page and the “Add it here” link in the reproduced flow; trace what leads to the Internal Server Error after an operation transfer. Check the draft and supplemental-draft paths and confirm the expected behavior for the original operator; done means adding a facility no longer fails after the transfer.

Written by the indexing model from the issue text.