Enh/dx 362 upgrade inquirer to v12

[harshithad0703]

Changes

1. Upgraded inquirer from v8.2.7 to v12.11.1 (5 packages)

• Packages: contentstack, contentstack-utilities, contentstack-bootstrap, contentstack-clone, contentstack-seed
• Maintains Node.js 14+ runtime compatibility
• Removes dependency on unmaintained inquirer-checkbox-plus-prompt
• Fixed deprecated BottomBar API usage in contentstack-clone
• Updated type imports for inquirer v12 compatibility in contentstack-utilities

2. Migrated contentstack-export-to-csv to @inquirer/prompts v8.2.1

• Complete rewrite of interactive prompts using modern @inquirer/prompts ecosystem
• Built-in search functionality (type to filter, space to select) replaces plugin-based search
• Removed unmaintained dependencies: inquirer-checkbox-plus-prompt, inquirer-autocomplete-prompt
• Updated Node requirement from unlimited to >=18.0.0

3. Upgraded TypeScript from v4.9.5 to v5.0.0 (17 packages)

• Required to support inquirer v12's const type parameter syntax
• Enables modern TypeScript features across the codebase
• No impact on runtime compatibility

4. Updated @types/node from v14 to v18 (6 packages)

• Required for TypeScript compilation with inquirer v12 type definitions

5. Plugins that use the inquirer table prompt

The table prompt is implemented in @contentstack/cli-utilities (inquirer-table-prompt.ts) and is used in one plugin only.
Plugin: @contentstack/cli-cm-branches (Branches)
Command: csdx cm:branches:merge
Package: packages/contentstack-branches
Usage: packages/contentstack-branches/src/utils/interactive.ts (two table prompts)

[gitguardian]

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
27413674	Triggered	Generic Password	f42ff37	pnpm-lock.yaml	View secret
27413675	Triggered	Generic Password	f42ff37	pnpm-lock.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[aman19K]

@harshithad0703 , since you've updated inquirer table code, could you pls list down in whichever plugins we're using it. According to me, we're using into branches. So that QA can verify it manually.

[harshithad0703]

@harshithad0703 , since you've updated inquirer table code, could you pls list down in whichever plugins we're using it. According to me, we're using into branches. So that QA can verify it manually.

Only @contentstack/cli-cm-branches uses inquirer table, updated PR description