NotificationConfig permission to edit only own needs account-id placeholder in permission/ability system

[sleidig]

original issue:

"Activate Notifications" button in toolbar section should close the popup (currently stay open after navigating to settings page)

After further investigation, the change detection works correctly but there can be problems due to permissions: The user needs to have "manage" permission on the own NotificationConfig entity. If that is not given, then the config cannot be synced and the system will remain in state without "activated" notifications.

---

For privacy and data management, each user should only have access to the own NotificationConfig entity (i.e. the doc where "conditions": { "_id": { "$eq": "${user.id}" } }). However, while we do have a placeholder for ${user.name} that reference the current user's linked profile entityId, we currently do not have the account (keycloak) ID available on the replication-backend's ability implementation yet.

https://github.com/Aam-Digital/replication-backend/blob/1090b71d0409596483a762c8a0965a327259ace9/src/auth/guards/jwt-cookie/jwt-cookie-strategy.service.ts#L30-L40
(and also JwtBearerStrategyService --> centralize and re-use code to map token to UserInfo object?)

[sleidig]

The default permissions should be:

    {
      "subject": "NotificationEvent",
      "action": "manage"
    },
    {
      "subject": "NotificationConfig",
      "action": "manage",
      "conditions": {
        "userId": "${user.id}"
      }
    },

[sleidig]

@tomwwinter , could you review the two PRs (replication-backend + frontend) for this?