Add ordering on bill number for more consistency

Bill number is a string, and doesn't sort correctly across years. So we still sort via date introduced first, then use bill number to break ties (bills introduced on the same day), which wouldn't have issues sorting bill numbers across years (since it's all on the same day).

Code reuse is a bit fucked, because this spans both the front-end and the back-end. The scraping order should be the same as the order shown to the user.

site/src/app/bills/page.tsx

@@ -14,6 +14,7 @@ async function getRecentBills() {
       "bill_no, name, second_reading_date_type, second_reading_date, is_passed, passed_date, summary, pdf_url",
     )
     .order("date_introduced", { ascending: false })
+    .order("bill_no", { ascending: false })
     .limit(20);
   if (error) throw error;
   return data;

supabase/functions/generate-bills-summary/index.ts

@@ -24,6 +24,7 @@ Deno.serve(async (req) => {
     .not("original_text", "is", null)
     .is("summary", null)
     .order("date_introduced", { ascending: false })
+    .order("bill_no", { ascending: false })
     .limit(1)
     .maybeSingle();
   if (selectError) throw selectError;

supabase/functions/scrape-bills-pdf/index.ts

@@ -52,6 +52,7 @@ Deno.serve(async (req) => {
     .select("id, pdf_url")
     .is("original_text", null)
     .order("date_introduced", { ascending: false })
+    .order("bill_no", { ascending: false })
     .limit(1)
     .maybeSingle();
   if (selectError) throw selectError;