feat(api): set scheduling InitiatedByUserId on batch and constraint publishes

[noamarg]

Summary

Populates InitiatedByUserId on SchedulePeriodRequest and HandleConstraintChangeRequest using the current JWT user, so asynchronous engine results can be correlated with the triggering operator.

Implementation details

• ScheduleController: User.GetUserId() on batch enqueue.
• UserConstraintService / ActivityConstraintService: IHttpContextAccessor + safe resolver for initiator guid.
• Tests: IHttpContextAccessor mock with null HttpContext where existing tests do not model a request.

Testing

dotnet test tests/Chronos.Tests.MainApi/Chronos.Tests.MainApi.csproj

• Manually: trigger batch or constraint change; inspect published JSON (optional) for initiatedByUserId in dev.

Risk / rollout

Low. Additive fields on messages; null initiator if unauthenticated or no HTTP context (should not occur for these authorized controller/service entry points in normal operation).

Rollback

Revert PR; messages revert to initiatedByUserId: null; notifications won’t target users until re-deployed.

Files in this PR (only)

• Chronos.Service/src/Chronos.MainApi/Schedule/Controllers/ScheduleController.cs
• Chronos.Service/src/Chronos.MainApi/Schedule/Services/UserConstraintService.cs
• Chronos.Service/src/Chronos.MainApi/Schedule/Services/ActivityConstraintService.cs
• Chronos.Service/tests/Chronos.Tests.MainApi/Services/Schedule/ActivityConstraintServiceTests.cs
• Chronos.Service/tests/Chronos.Tests.MainApi/Services/Schedule/UserConstraintServiceTests.cs

[adamrammal]

good job