ActivityLogPolicy.canCreate() incorrectly models automatic system logging as a user action

[annikaholmqvist94]

Body:

Problem

ActivityLogPolicy.canCreate() throws ForbiddenException for any non-ADMIN user.
This made sense if a user were manually creating log entries via an API endpoint,
but automatic logging is always triggered by the system — not by users directly.

Why it is wrong

When Anna (OWNER) creates a medical record, the system logs the event on her
behalf. The log is written by the system, not by Anna. Checking whether Anna
"has permission to write logs" is the wrong question entirely.

Fix

Remove the canCreate() call from ActivityLogService.log().
The canCreate() method in ActivityLogPolicy can be deleted unless a future
manual admin-only log endpoint is introduced.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• ActivityLogService.log() blocks OWNER and VET from creating medical records #116

🔗 Related PRs

#34 - Add Entities ActivityLog, enum ActivityType, Deletes CaseStatatus no usage, ActivityLogRepository and ActivityLogService [merged]
#63 - Add ActivityLogPolicy with role-based access control and immutable rules [merged]
#64 - Changes ActivityLogService with validation and null-safety [merged]
#70 - Changes ActivityLogService after ActivityLogController implements [merged]
#75 - Changes ActivityLogPolicy [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!