fix: PostgreSQL — demo data case sensitivity + add Lost Reason fixtures

Two fixes for v17/develop with PostgreSQL backend:

1. Demo data used 'Budget constraints' but the actual Lost Reason
   record is named 'Budget Constraints' (uppercase C). PostgreSQL
   string comparison is case-sensitive by default, while MariaDB
   uses case-insensitive collation. Fixed to match exact record name.

2. CRM Lost Reasons are required by demo data but were only defined
   in test_records.json (loaded during tests). Added them as app
   fixtures so they are created during bench install-app crm,
   ensuring demo data works on fresh installations.

Both fixes are backwards-compatible with MariaDB.

Author: skanderphilipp

crm/demo/deals.py

@@ -61,7 +61,7 @@ def create_demo_deals(lead_names, demo_users):
 			"deal_value": 55000,
 			"probability": 0,
 			"deal_owner": session_user,
-			"lost_reason": "Budget constraints",
+			"lost_reason": "Budget Constraints",
 			"lost_notes": "Q2 budget was cut. Leo said they would revisit in Q4 once headcount hiring is complete. Added to nurture sequence.",
 		},
 	)

crm/fixtures/crm_lost_reason.json

@@ -0,0 +1,27 @@
+[
+ {
+  "doctype": "CRM Lost Reason",
+  "name": "Price too high",
+  "lost_reason": "Price too high"
+ },
+ {
+  "doctype": "CRM Lost Reason",
+  "name": "Competition",
+  "lost_reason": "Competition"
+ },
+ {
+  "doctype": "CRM Lost Reason",
+  "name": "Budget Constraints",
+  "lost_reason": "Budget Constraints"
+ },
+ {
+  "doctype": "CRM Lost Reason",
+  "name": "No response",
+  "lost_reason": "No response"
+ },
+ {
+  "doctype": "CRM Lost Reason",
+  "name": "Not interested",
+  "lost_reason": "Not interested"
+ }
+]

crm/hooks.py

@@ -1,6 +1,8 @@
 app_name = "crm"
 app_title = "Frappe CRM"
 app_publisher = "Frappe Technologies Pvt. Ltd."
+fixtures = ["CRM Lost Reason"]
+
 app_description = "Kick-ass Open Source CRM"
 app_email = "shariq@frappe.io"
 app_license = "AGPLv3"