fix: admin group membership on install, and db_name breaking the db list

- group_school_administrator now includes base.user_admin, matching
  core Odoo's own convention (see hr.group_hr_manager) - otherwise
  every fresh install requires a manual trip to Settings > Users just
  to see this module's own menus.
- odoo.conf: drop db_name. Found by hand while testing: when db_name
  is set and dbfilter is not, Odoo's list_dbs() returns db_name's
  value verbatim instead of querying postgres, so the database
  selector shows only that one database no matter how many actually
  exist. Silently breaks O9's "swap to the second demo school in
  under five minutes" requirement, which depends on switching between
  multiple real databases.

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

addons/mc_education_base/security/mc_education_security.xml

@@ -39,6 +39,11 @@
         <field name="privilege_id" ref="privilege_school"/>
         <field name="implied_ids" eval="[(4, ref('group_school_staff'))]"/>
         <field name="comment">Full read/write on the academic structure: years, terms, programs, batches.</field>
+        <!-- Same convention core Odoo modules use (see hr.group_hr_manager):
+             the database's own Administrator account should not need a
+             manual group assignment just to see this module's menus after
+             install. -->
+        <field name="user_ids" eval="[(4, ref('base.user_admin'))]"/>
     </record>
 
     <!-- Portal roles -->

odoo.conf

@@ -5,6 +5,10 @@ db_host = db
 db_port = 5432
 db_user = odoo
 db_password = changeme_db_2026
-db_name = school
 proxy_mode = False
 list_db = True
+# Deliberately no db_name here: when db_name is set and dbfilter is not,
+# Odoo's list_dbs() returns db_name's value verbatim instead of querying
+# postgres - the database selector then shows only that one name no
+# matter how many databases actually exist. O9's "swap to the second
+# demo school in under five minutes" needs the real list.