feat(permissions): single registry for secretary and clinic-doctor permissions

The list of permissionable resources was duplicated in six places that had
already diverged: both permission entities, three admin UI files and the
SecretaryPermissions TypeScript interface. Adding a resource meant editing all
of them, so new pages borrowed an unrelated resource instead — five resource
pages sat on appointment_settings.view and treatment-cases on appointments.view.

PermissionCatalog is now the only place that says which resources and actions
exist. Each entity keeps its own DEFAULT_PERMISSIONS, but as role policy only;
a test asserts those defaults never name a resource the registry doesn't have.

getPermissions() merges the stored JSON over the role defaults, so a resource
added to the registry later resolves to the role default instead of silently
false for every existing row. Explicitly stored values are never overwritten,
and no data migration is needed.

Two asymmetries fixed along the way:
- ClinicDoctorPermission validated writes against its own DEFAULT_PERMISSIONS,
  so services.create/delete could never be stored for an invited doctor.
- DoctorSecretary had no validation at all and would store any key, and it only
  read $patch['resources'] — the admin SecretariesPage sends a flat map, so its
  permission edit silently did nothing. Both entities now accept either shape
  and filter through the registry.

New resources 'resources' and 'treatment' are registered with defaults chosen to
preserve today's effective access, since both pages are currently gated on a
borrowed resource.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tests/Clinic/ClinicDoctorPermissionTest.php

@@ -7,6 +7,7 @@ use App\Clinic\Entity\Clinic;
 use App\Clinic\Entity\ClinicDoctorPermission;
 use App\Clinic\Repository\ClinicDoctorPermissionRepository;
 use App\Doctor\Entity\Doctor;
+use App\Shared\Security\PermissionCatalog;
 use App\Tests\ApiTestCase;
 
 /**
@@ -46,8 +47,10 @@ class ClinicDoctorPermissionTest extends ApiTestCase
 
         self::assertSame(200, $this->responseCode());
         self::assertTrue($res['data']['active']);
+        // ترتیب و مجموعهٔ کلیدها را PermissionCatalog تعیین می‌کند، نه ترتیبِ
+        // نوشتنِ DEFAULT_PERMISSIONS؛ مقادیر همان پیش‌فرضِ نقش می‌مانند.
         self::assertSame(
-            ClinicDoctorPermission::DEFAULT_PERMISSIONS['resources'],
+            PermissionCatalog::merge([], ClinicDoctorPermission::DEFAULT_PERMISSIONS)['resources'],
             $res['data']['permissions']['resources'],
             'a member added before this feature gets defaults on first read',
         );