Replace File - Request History Comment Update

* As a user
* I want to know which file was replaced
* so that I can more easily identify changes - no NOTIFCATIONS, but COMMENTS are required

**Assumptions & Scope**
Currently when a user replaces a file, the generic batch of records uploaded notification is triggered. This can be misleading ,and we want to update the notification to be more helpful to users.

What is IN scope?
Notifications for replacing a file

**Acceptance Criteria**

**Scenario 1: User replacing file - Notification**
* GIVEN a user is on the records tab
* WHEN they replace a file from the records log
* THEN all assigned and watchers to the request will NOT receive the following notification:

**Scenario 1: User replacing file - System Generated Comment**
* GIVEN a user is on the records tab
* WHEN they replace a file from the records log
* THEN a system generated comment will be posted to the request history with the following message: "(User that took action) has replaced (old file name) with (new file name)"

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

Trace the records-tab file replacement flow and identify where the existing batch-upload notification and request-history comments are handled. Verify the replacement path suppresses the notification and records a comment containing the acting user, old file name, and new file name.

Written by the indexing model from the issue text.