fix: standardize command substitution syntax in Supabase template SQL scripts

- Updated command substitution syntax to use backticks consistently across SQL scripts.
- Ensured proper formatting for JWT and PostgreSQL user settings.

blueprints/supabase/template.yml

@@ -305,20 +305,20 @@ config:
         
     - filePath: /volumes/db/jwt.sql
       content: |
-        \\set jwt_secret \`echo "$JWT_SECRET"\`
-        \\set jwt_exp \`echo "$JWT_EXP"\`
+        \set jwt_secret `echo "$JWT_SECRET"`
+        \set jwt_exp `echo "$JWT_EXP"`
 
         ALTER DATABASE postgres SET "app.settings.jwt_secret" TO :'jwt_secret';
         ALTER DATABASE postgres SET "app.settings.jwt_exp" TO :'jwt_exp';
     - filePath: /volumes/db/logs.sql
       content: |
-        \\set pguser \`echo "$POSTGRES_USER"\`
+        \set pguser `echo "$POSTGRES_USER"`
 
         create schema if not exists _analytics;
         alter schema _analytics owner to :pguser;
     - filePath: /volumes/db/realtime.sql
       content: |
-        \\set pguser \`echo "$POSTGRES_USER"\`
+        \set pguser `echo "$POSTGRES_USER"`
 
         create schema if not exists _realtime;
         alter schema _realtime owner to :pguser;