Enhance Exclude Pattern Selection with Suggested Options and Usage-Based Recommendations

[filipchristiansen]

A more user-friendly way to manage exclude patterns could be implemented, potentially with the following features:

1. Dropdown/Checkbox Menu for Common Patterns:

   • Allow users to easily select common exclude patterns (e.g., *.csv, *.toml, /tests, *.log, etc.).
   • These patterns could be pre-populated based on common exclusions or usage statistics.

2. Repo-Specific Suggestions:

   • After the user runs gitingest on a repository, analyze the file types and structures to suggest exclude patterns specific to the repo. For example:
     • Identify patterns that would significantly reduce the token count.
     • Highlight those patterns in the suggested list.

3. Usage-Based Ordering:

   • Order suggested patterns based on global usage statistics (how frequently they are excluded by other users) or the impact they have on the token count for the specific repository being analyzed.

This feature would improve usability by streamlining the process of excluding unnecessary files and directories, helping users optimize their token budgets while interacting with gitingest.

[cyclotruc]

This pre-filling of include/exclude patterns is definitly something I plan on adding in an "advanced settings" menu in the future

The main goal is to provide a good default experience with hidden configuration options
All the advanced settings combined together will become a "ingestion preset" that stays broad and high level (like: docs, architecture, implementation)

As we discussed with @filipchristiansen, we could probably sync those settings locally in a .gitingest file format (toml, yml?)