feat: standardize status change activity logging

[anonymoususer72041]

Summary

This PR standardizes pipeline status changes by separating the dedicated changeStatus flow from the generic activity flow and by using the status change activity types introduced in #737.

Instead of relying on a manually editable activity note during a status change, the resulting activity entry is now derived from the selected status change type. This makes status change logging more consistent and reduces manual variation in these entries.

To support this behavior, the previous combined addActivityChangeStatus flow is split into dedicated addActivity and changeStatus actions and templates. The related candidate and job order pipeline UI, permissions and tests are updated accordingly.

Motivation

The main goal of this change is to make status changes more standardized and less dependent on manual note editing.

Previously, changing a status was tied to a flow where the activity note could be freely adjusted, which made status change logging less consistent. By moving status changes into a dedicated flow and using the status change types added in #737, the system can create more predictable and uniform activity entries for these actions.

Splitting the modal is therefore not the primary objective by itself, but a necessary step to support a more guided and standardized status change workflow.