refactor(resource): drop the branch domain from resources

Resources never needed a branch: devices and rooms belong to the clinic
itself, and the picker always had exactly one option — a mandatory click
that decided nothing.

- `address_uuid` is now optional on resource and pool creation; when it is
  missing the environment's own address is used. Clients still sending it
  keep working.
- The panel no longer asks for or displays a branch anywhere: resource
  form, list column and filter, pool form and column, detail row, and the
  resource-first booking page.
- Availability no longer gates on `doctor_addresses.active`. That gate shut
  down every device of a clinic whose address row happened to be inactive,
  with a message no page in the panel could act on — no endpoint writes
  that column at all.

`address_id` stays on the resource: the timezone and the tenant pair are
derived from it. It is simply no longer the user's decision.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

assets/admin/components/resources/ResourceServicesPanel.tsx

@@ -36,7 +36,7 @@ interface Props {
 const SOURCE_LABELS: Record<string, string> = {
   resource_option:  'همین منبع',
   resource_service: 'منبع، روی سرویس والد',
-  branch:           'شعبه',
+  branch:           'تنظیم محل نوبت‌دهی',
   service_default:  'پیش‌فرض سرویس',
 };