Request Type update on AXIS's FOI Request updates its REQUESTID, leaving corresponding FLOW request obsolete

**Describe the bug in current situation**
Request Type update on AXIS's FOI Request updates its REQUESTID, leaving corresponding FLOW request obsolete . Whenever an update happens to a request type on AXIS's request - that application creates or assigns a new REQUEST ID on axis. This will affect AXIS Sync process on our FOI FLOW App. Why because, when new AXIS REQID gets generated, the older ID on FOI FLOW will NOT get triggered for SYNC. Also, if there are any work done on FOI FLOW from ministry coordinators will get obsolete , which might need to be moved MANUALLY to new REQ on FLOW - as per current design. suggestion is to make AXIS Request ID editable on FLOW to fix this issue appropriately. So that no work will get lost.


**Link bug to the User Story**

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

High
**Chance of Occurring (high/medium/low/very low)**

Low.
Discussed with Business team @m-prodan , @lmullane and dev teams - decided like, this is very low chance to happen.

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

Create a FOI FLOW request which is in sync with its corresponding AXIS request

**Steps to Reproduce**
Steps to reproduce the behavior:
1. After the pre-condition step, Go AXIS find the AXIS request and change the request type and save. We can see the AXIS Request ID getting updated and leaving previous AXIS request ID- non existing. But AXIS preserves all its meta data, and details
2. Open the FOI FLOW corresponds to it and See the Sync trigger -
3. Sync wont work, since OLDER AXIS Request ID is currently not existing.
4. So all work done on FOI FLOW's request like comments, Attachments , Div. stages etc need to be moved manfully - creates more work.

**Actual/ observed behaviour/ results**

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

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

No files or tests are named. Start by reproducing the AXIS request-type change and tracing the FOI FLOW sync trigger that uses the AXIS request ID; define done as preserving existing FLOW comments, attachments, and stages while synchronizing the request after its AXIS ID changes.

Written by the indexing model from the issue text.