Addressed and resolved the cli command for chatpickle

[jellyfishing2346]

This PR addresses the long-standing issue where the chatpickle CLI command was not recognized when run directly (Resolves #33). The following changes were made:

• Updated package.json bin field to the compiled JavaScript file instead of the TypeScript source.
• Ensured all required runtime dependencies (cucumber, aws-sdk, lodash.get, etc.) are installed.
• Added missing type definitions for Node.js.
• Added a sample chatpickle.config.json to the project root for CLI configuration.
• Updated the build process to output the correct files.

[arsena]

@copilot resolve merge conflicts

[Copilot]

Pull request overview

This PR introduces a compiled Node.js CLI entrypoint for Chatpickle and adjusts packaging/build settings so the chatpickle binary can be installed and executed as a proper npm “bin” command (addressing #33).

Changes:

• Added a new CLI entrypoint (src/cli.ts) that runs Cucumber with Chatpickle’s step support and default feature path handling.
• Updated package.json bin path and bumped several dependency/devDependency versions.
• Added a sample chatpickle.config.json at the repository root.

Reviewed changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/cli.ts	New Node CLI entrypoint that wires Cucumber to Chatpickle’s cucumberSupport and feature discovery logic.
package.json	Adjusts published binary path and updates dependency/devDependency versions.
chatpickle.config.json	Adds an example configuration file for running Chatpickle.

---

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

[jellyfishing2346]

Hi @arsena, I have just resolved the merge conflicts.