feat: Make Taste enable/disable project specific, not global

[dthyresson]

Summary

From my experience, enabling/disabling taste appears to be a global setting. If I have two cmd session, one where taste is addable and a second where I then disable taste, if I relaunch cmd within the project where in had been enabled it is now off.

--> I didn't notice this and was confused why my use wasn't being steered properly and I thought taste was completely broken. I only then noticed that the tase info in bottom right was gone.

Expected Behavior

Taste should be enabled or disable on a per project basis.

Taste Learning │
│ Configure taste learning preferences for this project

as it specifically references "this project.

Actual Behavior

It's a global setting (it seems).

Steps to reproduce the issue

1. launch cmd. enable taste. cli in project A
2. launch another cmd session. disable taste. cli in project B

3. quit cli in project A (keep b open where disabled)
4. launch cmd cli in project A again
   and now can see taste is disabled

but I never disabled in this project and I want to use taste in it

Command Code Version

0.32.3

Operating System

macOS

Terminal/IDE

ghostty

Shell

zsh

Additional context

The change in taste setting also happens when you start a new session like switching a model. So if in project A I enable taste and use deepseek flash and then in project b I disable and then go back to project a cli and switch model to gemini flash, taste gets disabled in cli for project a