Feat/financial position

[austin047]

Description

• AI chat fixes and improvements
• Implementation for financial position
• Implementation for holdings

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[sourceant]

Code Review Summary

This PR implements the 'Financial Position' and 'Holdings' features, including database schema updates, remote data sources, repositories, and UI screens. It also enhances the AI chat experience and improves exchange rate handling by shifting the logic to the backend.

🚀 Key Improvements

• Introduction of TransactionIntent to classify money movement (loans, investments, etc.) beyond simple income/expense.
• Offline-first approach for Financial Position using a dedicated cache table.
• Structured holding management with support for both manual and auto-priced (CoinGecko) assets.

💡 Minor Suggestions

• Centralize currency formatting logic into a single utility class.
• Update non-English translation files to fix placeholders and untranslated English keys.

🚨 Critical Issues

• Database migration v5 -> v6 is missing on_delete or on_update constraints for new FK-like references if they existed, though current implementation seems to follow existing patterns.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

The translation is set to English. It should be translated to German.

Suggested change

	"groups": "Groups",
	+ "groups": "Gruppen",

[sourceant]

Hardcoding the screen height ratio can cause issues on devices with unusual aspect ratios or when the keyboard is open. It is better to rely on the sheet's built-in scrollable behavior or provide a more flexible constraint.

Suggested change

	maxHeight: MediaQuery.of(context).size.height * maxHeightRatio,
	maxHeight: MediaQuery.sizeOf(context).height * maxHeightRatio,

[sourceant]

Mapping the rates and then manually adding the base key is redundant. The backend usually provides this, but if synthesizing, ensure null safety for the value conversion.

Suggested change

	final rates = (data['rates'] as Map<String, dynamic>).map(
	final rates = (data['rates'] as Map<String, dynamic>).map(
	(key, value) => MapEntry(key, (value as num).toDouble()),
	)..putIfAbsent(base, () => 1.0);