feat: Implement resource-based appointment booking flow

- Updated DoctorPage component to accept bookingResources prop for appointment list.
- Added serviceQuery function to serialize service item UUIDs for API requests.
- Introduced new API endpoints for fetching booking resources and resource slots.
- Enhanced tests for new resource-based booking functionality, including resource selection and service availability.
- Created ResourceSelect component for selecting appointment types, including doctor and resource options.
- Updated appointment submission logic to include resource_uuid in payload when applicable.
- Ensured UI reflects changes in booking flow without disrupting existing doctor-centric experience.

components/doctor/index.js

@@ -15,7 +15,7 @@ const specialtyHref = (name) => {
   return slug ? `/specialties/${slug}` : `/doctors?specialty=${encodeURIComponent(name)}`;
 };
 
-function DoctorPage({ doctor, comments, rateAggregate, addresses, bookableAddressUuids = [], bookingLocations = [], slug, faq = [] }) {
+function DoctorPage({ doctor, comments, rateAggregate, addresses, bookableAddressUuids = [], bookingLocations = [], bookingResources = [], slug, faq = [] }) {
   const { primary: primarySpecialty } = splitSpecialties(doctor?.specialties);
 
   return (
@@ -52,7 +52,12 @@ function DoctorPage({ doctor, comments, rateAggregate, addresses, bookableAddres
           addresses={addresses}
           bookableAddressUuids={bookableAddressUuids}
         />
-        <AppointmentList doctor={doctor} doctorSlug={slug} bookingLocations={bookingLocations} />
+        <AppointmentList
+          doctor={doctor}
+          doctorSlug={slug}
+          bookingLocations={bookingLocations}
+          bookingResources={bookingResources}
+        />
       </div>
       <ClaimProfileSection doctor={doctor} />
       <Faq items={faq} />