Implemented sync functionality with sheets and email sending

.github/copilot-instructions.md

@@ -91,6 +91,7 @@ onsubmit|preventDefault={handleSubmit} is depracated, do not use it!
 
 Loading session using page.server.ts is not needed as the session is already available in the locals object.
 
+Do not use import { page } from '$app/stores'; as it is deprecated! Use instead: import { page } from '$app/state'; 
 
 IMPORTANT: Always make sure that the client-side module are not importing secrets
 or are running any sensritive code that could expose secrets to the client.
@@ -100,6 +101,8 @@ fetch data from there instead of directly in the client-side module.
 The database schema in supabase is as follows:
 -- WARNING: This schema is for context only and is not meant to be run.
 -- Table order and constraints may not be valid for execution.
+-- WARNING: This schema is for context only and is not meant to be run.
+-- Table order and constraints may not be valid for execution.
 
 CREATE TABLE public.events (
   id uuid NOT NULL DEFAULT gen_random_uuid(),
@@ -142,6 +145,7 @@ CREATE TABLE public.participants (
   scanned_at timestamp with time zone,
   scanned_by uuid,
   section_id uuid,
+  email_sent boolean DEFAULT false,
   CONSTRAINT participants_pkey PRIMARY KEY (id),
   CONSTRAINT participants_created_by_fkey FOREIGN KEY (created_by) REFERENCES auth.users(id),
   CONSTRAINT participants_event_fkey FOREIGN KEY (event) REFERENCES public.events(id),
@@ -167,8 +171,3 @@ CREATE TABLE public.sections (
   CONSTRAINT sections_pkey PRIMARY KEY (id)
 );
 
-An event is created by calling RPC databse function create_event
-by passing the following parameters: 
-- name, date, email_subject, email_body, sheet_id, name_column, surname_column, email_column, confirmation_column
-
-