feat(VEG-3430): Add the Connector bundle logic into the cli

[saikambaiyyagari]

Description

This PR introduces a new zcli connectors bundle command that provides a streamlined way to bundle Zendesk connectors for deployment. The command uses Vite as the bundling engine and includes asset copying, translation handling, and manifest generation.

2822f16 Add the manifest generator logic to generate the connector manifest

16d1587 Introduce the connector bundle logic to create the minified JS output

dea5d1c Add codeowners

5c56bb4 Refactor and structure the code

Detail

JIRA: https://zendesk.atlassian.net/browse/VEG-3430

Checklist

• 💂‍♂️ includes new unit and functional tests

[Copilot]

Pull request overview

This pull request introduces a new zcli connectors bundle command that provides a streamlined way to bundle Zendesk connectors for deployment. The implementation uses Vite as the bundling engine and includes automated asset copying, translation handling, and manifest generation capabilities.

Changes:

• Added new connectors bundle command with support for watch mode and custom output directories
• Implemented Vite-based bundling infrastructure with Babel transpilation targeting IE11 compatibility
• Created manifest generator to automatically generate connector manifest files from bundled output
• Refactored test files in zcli-core for better test isolation and cleanup
• Added new dependencies: Vite, Rollup plugins, ora spinner, and sinon-chai for testing

Reviewed changes

Copilot reviewed 15 out of 16 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
packages/zcli-connectors/src/commands/connectors/bundle.ts	New bundle command implementation with flag parsing and error handling
packages/zcli-connectors/src/lib/vite/vite-config.ts	Vite configuration builder with asset/translation copying and manifest generation plugins
packages/zcli-connectors/src/lib/vite/vite-runner.ts	Vite runner wrapper that executes builds and handles errors
packages/zcli-connectors/src/lib/manifest-generator/generator.ts	Manifest generator that creates manifest.json from bundled connector
packages/zcli-connectors/tests/functional/bundle.test.ts	Comprehensive tests for bundle command functionality
packages/zcli-connectors/src/lib/vite/vite-config.test.ts	Tests for Vite configuration builder and plugins
packages/zcli-connectors/src/lib/vite/vite-runner.test.ts	Tests for Vite runner error handling and build process
packages/zcli-connectors/src/lib/manifest-generator/generator.test.ts	Tests for manifest generation and validation
packages/zcli-core/src/lib/config.test.ts	Refactored tests with proper stub lifecycle management
packages/zcli-connectors/tsconfig.json	Removed esModuleInterop setting
packages/zcli-connectors/package.json	Added bundling-related dependencies and dev dependencies
.github/CODEOWNERS	Added Vegemite team as owners of connectors package
yarn.lock	Lock file updates for new dependencies

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 15 out of 16 changed files in this pull request and generated 12 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[mtsolakiszen]

Should this be before the output directory creation?

[saikambaiyyagari]

We are printing the resolved absolute paths for output and the input based on the flags or default values. The logic code path above these print statements. Can we leave it here?

[mtsolakiszen]

Sure, not a blocker on my end. Just wanted to call out the output order would be:

Created output directory: ${outputPath}

Verbose mode enabled
Input path: ${inputPath}
Output path: ${outputPath}
Watch mode: enabled

Which seems a bit odd. As a user I would expect:

Verbose mode enabled
Input path: ${inputPath}
Output path: ${outputPath}
Watch mode: enabled

Created output directory: ${outputPath}
...

[saikambaiyyagari]

Renamed the labels like this for now:
Resolved Input path: ${inputPath}
Resolved Output path: ${outputPath}