[Breaking] Renamed MISTRALAI to MISTRAL everywhere

[Sixzero]

MISTRALAI I think was deceptive, as everywhere out there it is called MISTRAL_API_KEY.

[Sixzero]

I doubt too many people would use Mistral models, but I hope they can also adjust this in their env vars. Although I see they need to be aware of the change.

In their docs it is called MISTRAL_API_KEY: https://docs.mistral.ai/getting-started/quickstart/

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 2 lines in your changes missing coverage. Please review.

Project coverage is 91.98%. Comparing base (bfc8833) to head (b91160d).
Report is 5 commits behind head on main.

Files with missing lines	Patch %	Lines
src/llm_openai_schema_defs.jl	50.00%	1 Missing ⚠️
src/user_preferences.jl	75.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #231      +/-   ##
==========================================
+ Coverage   91.93%   91.98%   +0.04%     
==========================================
  Files          47       47              
  Lines        4601     4640      +39     
==========================================
+ Hits         4230     4268      +38     
- Misses        371      372       +1     

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

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[svilupp]

@Sixzero Could you please add a new section at the top of the changelog record that is a breaking change and explain it there? See past examples. The idea is to make it stand out / make it easy to see when some breaking changes happened

[Sixzero]

Good idea!

[Sixzero]

Added the legacy support.

On a sidenote:
Actually AISH.jl couldn't generate the solution, had to do it manually, because the file is 55k character long and most LLMs can only generate 8000 tokens as output, so for long files I guess "Instant Apply" should switch back to some legacy diffing solution.

[svilupp]

Awesome! Thank you! I've just added the note to the changelog as a breaking change.