Records tab - Change Division - Not prompting a restitching/download of Harms Package

**Describe the bug in current situation**

A user uploads all their responsive records to the Records tab, and then downloads for harms. If the user then bulk changes the divisions in the Records tab, they are not prompted to re-stitch/download the harms package. This leads to the harms package not reflecting the division change, and producing an inaccurate package.

Workaround is to just delete and re-add a file, or replace a file with the same file, to prompt a restitching.

**Link bug to the User Story**

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

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

**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 records in the Records tab, with two or more division tags available
2. Select to Download for Harms
3. Next, select files to bulk change the divisional tag on
4. Change the divisional tag and save
5. See error where 'Download for Harms' is not being prompted to restitch, and you can only download the outdated Harms package

**Actual/ observed behaviour/ results**

Harms package is not requiring a restitch after records have their divisional tag changed through the bulk actions. This leads to an out of date Harms package for download.

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

GIVEN a user has previously downloaded for harms
WHEN the user changes the divisional tag on records
THEN the 'Download for Harms' will prompt the user to restitch the package
AND the harms package will reflect the divisional tag changes

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

Start by reproducing the workflow in the Records tab: download for harms, bulk-change a division tag, and check whether the prompt appears. Trace the bulk division update and the Download for Harms state; done means a changed tag prompts restitching and the resulting harms package reflects the change.

Written by the indexing model from the issue text.