feat: add config-bundle readonly TUI

[nborges-aws]

Description

Adds an interactive, read-only TUI for eval config-bundle command tree. Bare read-only commands now open TUI flows instead of returning missing flag errors, while mutating commands remain CLI-only

Screens

Path	Screen
eeval config-bundle	RouterScreen menu
eval config-bundle list / eval config-bundle get	ConfigBundlePicker using PaginatedTablePicker
eval config-bundle get/:bundleId	JsonDetail
eval config-bundle version	RouterScreen menu
eval config-bundle version list	ConfigBundlePicker for bundle selection
eval config-bundle version list/:bundleId	ConfigBundleVersionPicker using PaginatedTablePicker
eval config-bundle get/:bundleId/:versionId	version in JsonDetail

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update
• Other (please describe):

Testing

How have you tested the change?

• Added config-bundle.screen.test.tsx covering menu filtering, navigation, metadata rendering, pagination calls, latest and immutable version retrieval, sorting, retries, and empty/error states.

• Added command-dispatch coverage confirming only read-only leaves open the TUI.

• bun test src/handlers/eval (233 pass, 0 fail)

• I ran npm run test:unit and npm run test:integ

• I ran npm run typecheck

• I ran npm run lint

• If I modified src/assets/, I ran npm run test:update-snapshots and committed the updated snapshots

Checklist

• I have read the CONTRIBUTING document
• I have added any necessary tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
• My changes generate no new warnings
• Any dependent changes have been merged and published

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.09%. Comparing base (94f890c) to head (7a0f500).

Additional details and impacted files

@@             Coverage Diff              @@
##           refactor    #2024      +/-   ##
============================================
+ Coverage     97.06%   97.09%   +0.03%     
============================================
  Files           374      381       +7     
  Lines         22542    22778     +236     
============================================
+ Hits          21880    22116     +236     
  Misses          662      662              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Hweinstock]

is there a reason we don't also support get? Not saying I agree with the standard, but so far, I believe each screen has routed get and list to the same page.

[nborges-aws]

The CLI supports config-bundle get, config-bundle list and config-bundle version list. We mirror that in the TUI, so the flow of screens is config-bundle -> get, list, or version. If version is selected: version -> list. The only child command version exposes is list for either CLI or TUI flow