feat: show checkedName for selected checkbox options

[Sakthieswaran-tech]

This PR updates the checkbox prompt to display the checkedName property for selected options,
falling back to name if checkedName is not provided. It includes:

• Updated normalizeChoices to handle checkedName.
• Updated renderItem logic to display checkedName when an item is checked.
• Test case added to verify the behavior.

This improves the clarity of selected options in prompts without breaking existing functionality.

Resolves #1647

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@f4579f4). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1844   +/-   ##
=======================================
  Coverage        ?   95.74%           
=======================================
  Files           ?       45           
  Lines           ?     2772           
  Branches        ?      750           
=======================================
  Hits            ?     2654           
  Misses          ?      109           
  Partials        ?        9           

☔ View full report in Codecov by Sentry.
📢 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.

[Sakthieswaran-tech]

Hey @SBoudrias
I noticed that after adding checkedName internally in Choice, all local tests pass, but the e2e demo fails with this TypeScript error:
Object literal may only specify known properties, and 'checkedName' does not exist in type 'Separator | Choice'
I think the issue is related to the types exposed publicly in the checkbox package. I’m not 100% sure what the preferred approach is here — should checkedName be added to the public Choice type in CheckboxConfig, or exported separately, or handled some other way?

[Sakthieswaran-tech]

Hey @SBoudrias ,

I’m still running into a TypeScript issue with the checkedName property. After adding it internally in Choice, all local tests pass, but the e2e demo fails with:

Object literal may only specify known properties, and 'checkedName' does not exist in type 'Separator | Choice'

I’ve checked the types exposed publicly in the checkbox package and I’m unsure what the preferred approach is. Should checkedName be added to the public Choice type in CheckboxConfig, exported separately, or handled another way?

I’d appreciate your guidance so I can finalize the PR. Thanks!

[SBoudrias]

I believe it's an issue with the e2e test itself - we never added a new type this way, so the test didn't run into this case where it needs to whole package re-generated.

[Sakthieswaran-tech]

Hey @SBoudrias , thanks a lot for looking into this and fixing the e2e issue — really appreciate it!
Let me know if there’s anything you’d like me to update or re-run on my side to help get this merged.

[SBoudrias]

This is what's breaking the e2e test.

Resources:

• https://yarnpkg.com/configuration/manifest#resolutions
• https://yarnpkg.com/cli/set/resolution

yarn set resolution <descriptor> <resolution>

The <descriptor> isn't correct to link the prompt packages required by @inquirer/prompts to use the one from the repo.

I'm short on time to figure the exact syntax, but that's the problem. Hopefully it gives you enough to research a bit the issue 🤞🏻