chore : rename Coltura to Starseed

- Rename project name across code, configs, docs, dev/prod infra
- Dev: DOCKER_APP_NAME + POSTGRES_DB switched to starseed, containers become php-starseed-fpm / nginx-starseed / starseed-db-1
- Dev: mount nginx.conf on default.conf instead of starseed.conf to avoid alphabetical-order clash with image's default site
- Makefile: export CURRENT_UID/CURRENT_GID at top level so docker compose builds (db-reset etc.) get them
- Prod: image registry path, container_name, volumes, vhost server_name + paths, DATABASE_URL, CORS, CI workflow
- Add doc/prompt-rename-prod.md with the migration runbook for the prod server (DB rename, FS move, vhost, Let's Encrypt)

frontend/tailwind.config.ts

@@ -1,7 +1,7 @@
 import type {Config} from 'tailwindcss'
 
 /**
- * Config Tailwind du projet Coltura.
+ * Config Tailwind du projet Starseed.
  *
  * @nuxtjs/tailwindcss merge automatiquement les configs de chaque layer
  * Nuxt declare dans `nuxt.config.ts:extends`. Le layer `@malio/layer-ui`
@@ -11,7 +11,7 @@ import type {Config} from 'tailwindcss'
  *    success,btn-*,site-blue,site-yellow,site-green}
  *  - fontFamily.sans (Helvetica Neue)
  *
- * Cette config locale ne redeclare QUE ce qui est specifique a Coltura
+ * Cette config locale ne redeclare QUE ce qui est specifique a Starseed
  * ou absent de la config Malio — evite la duplication et les derives.
  */
 export default <Partial<Config>>{
@@ -19,7 +19,7 @@ export default <Partial<Config>>{
     theme: {
         extend: {
             colors: {
-                // Couleurs applicatives Coltura (hors namespace `m` reserve
+                // Couleurs applicatives Starseed (hors namespace `m` reserve
                 // au design system Malio partage).
                 primary: {
                     500: '#222783',