fix(doctor): derive booking state from booking_locations

The profile decided "نوبت‌دهی غیرفعال است" from `doctor.active` alone, while the
page already had `booking_locations` — the more precise source, since the backend
only returns locations that are genuinely bookable. The two could disagree, and
for a doctor bookable only at a clinic they did.

A shared `bookingState` helper now drives both the desktop card and the mobile
bar: any location means bookable, the label comes from the earliest
`next_available_at`, and locations with no capacity yet read as "فعلاً نوبت خالی
ندارد" rather than disabled. With no locations at all it falls back to the
previous `doctor.active` / `free_turn` fields.

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

components/doctor/index.js

@@ -5,7 +5,7 @@ import DetailDoctor from "./detailDoctor";
 import Share from "./detailDoctor/Share";
 import CustomLoading from "@/app/component/loading/Custom";
 
-function DoctorPage({ doctor, comments, rateAggregate, addresses, bookableAddressUuids = [], slug }) {
+function DoctorPage({ doctor, comments, rateAggregate, addresses, bookableAddressUuids = [], bookingLocations = [], slug }) {
   return (
     <div className="pt-[92px] sm:pt-[120px] mt:pt-[148px] lg:pt-[176px] mt-[px] padding-responsive">
       <div className="flex items-center justify-between">
@@ -41,7 +41,7 @@ function DoctorPage({ doctor, comments, rateAggregate, addresses, bookableAddres
           addresses={addresses}
           bookableAddressUuids={bookableAddressUuids}
         />
-        <AppointmentList doctor={doctor} doctorSlug={slug} />
+        <AppointmentList doctor={doctor} doctorSlug={slug} bookingLocations={bookingLocations} />
       </div>
       <ClaimProfileSection doctor={doctor} />
     </div>