feat: deployment config & unified service name

[mbani01]

This pull request updates the Snowflake connectors service to use the new snowflake-connectors-worker naming convention across environment configuration, Docker, and service definitions. The changes ensure consistency in naming and configuration, which helps clarify the role of the worker service and prevents confusion with previous connector naming.

Naming and configuration updates:

• Updated all references from snowflake-connectors to snowflake-connectors-worker in environment variables, Dockerfile paths, and service names within the package.json scripts for the Snowflake connectors app.
• Renamed the Docker Compose YAML file from snowflake-connectors.yaml to snowflake-connectors-worker.yaml, and updated service names and hostnames to use snowflake-connectors-worker instead of snowflake-connectors. [1] [2] [3]
• Added a new environment configuration file snowflake-connectors-worker.env specifying the Dockerfile, context, repository, and services for the worker.

---

Note

Low Risk
Config-only renaming for build/compose and runtime env vars; primary risk is deployment/runtime breakage if any external references still expect the old snowflake-connectors service name.

Overview
Standardizes the Snowflake connectors deployment to the snowflake-connectors-worker service name across build and runtime configuration.

Adds a new build env config (scripts/builders/snowflake-connectors-worker.env) and updates the compose definition (scripts/services/snowflake-connectors-worker.yaml) to use the worker-specific Dockerfile and service/hostname names. Updates services/apps/snowflake_connectors/package.json scripts so start/debug and trigger-export run with SERVICE=snowflake-connectors-worker.

^{Written by Cursor Bugbot for commit f518ce1. This will update automatically on new commits. Configure here.}

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

[github-actions]

⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.