feat: filter search for commit change type

[Yusin0903]

Description

Added search filter functionality to commit type selection in Conventional Commits. This allows users to quickly find commit types by typing part of the type name or description, enhancing user experience especially when working with many commit types.

Changes Made

1. Added use_search_filter: True to enable search filtering in the commit type selection.
2. Set use_jk_keys: False to prevent conflicts with search functionality (as j/k keys can be part of the search term).
3. Because the interaction questionary can not test directly so I test to verify search filter functionality and parameter works correctly.
4. Added newline at the end of file to comply with PEP 8 standards.

Checklist

• Add test cases to all the changes you introduce
• Run poetry all locally to ensure this change passes linter check and test
• Test the changes on the local machine manually
• Update the documentation for the changes

Expected behavior

When a user types characters during commit type selection, the list of options is filtered to show only those containing the typed characters. For example, typing "fix" will show the item that contains "fix" .

Steps to Test This Pull Request

1. Run cz commit to start the commit process
2. When the commit type selection appears, type what you want to search. eg: "fix"
3. Verify that the list filters to show the all "fix" items
4. Try other search terms to confirm filtering works as expected

Additional context

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.51%. Comparing base (120d514) to head (5c52c3d).
Report is 579 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1381      +/-   ##
==========================================
+ Coverage   97.33%   97.51%   +0.17%     
==========================================
  Files          42       57      +15     
  Lines        2104     2655     +551     
==========================================
+ Hits         2048     2589     +541     
- Misses         56       66      +10     

Flag	Coverage Δ
unittests	97.51% <ø> (+0.17%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ 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.

[Lee-W]

I don't know whether we should set it as the default, probably not for v4. I would suggest making it configurable. Also, this now only works for conventional_commits, we would like it to work for all cz rules. Following up with this discussion, we probably could make the whole questionary behavior configurable, but that could be another PR

[Yusin0903]

Thanks for the review! I will modify the search function to work for all cz rules. As for making it configurable, we can open another issue for that. Does that sound good?

[Lee-W]

I would probably say we should make it configurable first to retain the current behavior and let those who want to play with it opt in

[Yusin0903]

Hi @Lee-W,

I have tested the search filter functionality using the configuration approach:

[[tool.commitizen.customize.questions]]
type = "list"
name = "change_type"
message = "Select the type of change you are committing"
use_search_filter = true
use_jk_keys = false

It works as expected, so I've:

• Removed the modifications to conventional_commits.py
• Added documentation for the feature in customization.md
• Added test cases to verify the functionality
  The search filter can now be enabled through configuration without modifying the core code.