Consultations - Divisional Tracking Comments

* As a Ministry Coordinator
* I want divisional tracking changes to be posted in the comment log of my consultation
* so that I can better track the history of the consult

**Assumptions & Scope**
This represents the need for divisional tracking changes and updates to be reflected in the comments as part of the request history tag.

The automated comments of consult divisional tracking should work the same as it currently exists for divisional tracking with FOI Requests

**Acceptance Criteria**

**Scenario 1: System Generated Comment Structure**
* GIVEN the ministry coordinator has updated a divisional stage(s) on a Consultation
* WHEN the comment is generated
* THEN the note will show FOI App as the "username" with a date and time stamp
* AND the note will be ordered with the same logic as #584 (newest to oldest)

Scenario 2: Divisions Selected for Call for Records
* GIVEN a Ministry coordinator is on the review consultation page
* WHEN a new division(s) AND stage is selected from the request tracking section
* THEN the application will automatically generate a comment with the text that "Division Name(s) stage selected (Drop down selection)

**Scenario 3: Changes to Division Stages**
* GIVEN a Ministry coordinator has already selected divisions for tracking
* WHEN the division stage drop down is activated, and a new stage selected
* THEN the application will automatically generate a comment with the following text "(Division Name) stage selected (Drop down selection)"

**Scenario 4: Division removed**
* GIVEN a Ministry coordinator has already selected divisions for tracking
* WHEN the user deletes the division
* THEN the application will automatically generate a comment with the following text "(Division Name) removed (Drop down selection)"

**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?

Start by reviewing the existing divisional tracking behavior for FOI Requests and the consultation review page's request tracking section. Compare the needed comment ordering with issue #584. Done means comments are generated for division and stage selection, stage changes, and division removal, with the specified text, FOI App attribution, and timestamps.

Written by the indexing model from the issue text.