feat(migration): migrate legacy owner data and update config reference handling

- Implemented a migration process to move resources from the legacy owner "default" to the new default owner "local", ensuring no data loss during the transition.
- Updated configuration reference handling to replace legacy `$VAR_`, `$SECRET_`, and `$CONTEXT_` prefixes with mustache-style `{{ vars.name }}`, `{{ secrets.name }}`, and `{{ context.name }}`.
- Enhanced YAML configuration files and scripts to reflect the new mustache syntax, improving consistency across the application.
- Added tests to validate the migration process and ensure proper handling of legacy references.
- Updated documentation to guide users on the new configuration reference format.

plugins/joplin-api/script.js

@@ -198,7 +198,7 @@ joplinHttp.meta = {
     token: {
       type: "string",
       required: true,
-      description: "Bearer token ($SECRET_); Bearer prefix is added if missing",
+      description: "Bearer token ({{ secrets.* }}); Bearer prefix is added if missing",
     },
     timeoutMs: {
       type: "number",
@@ -237,7 +237,7 @@ joplinHttp.meta = {
     config: {
       url: "http://10.8.0.6:3030/notes",
       method: "GET",
-      token: "$SECRET_joplin_api_token",
+      token: "{{ secrets.joplin_api_token }}",
       timeoutMs: 60000,
     },
   },