Fix Custom Fields Manager tab persistence bug

[valentinMERCIER]

Summary

Fixes the issue where custom fields created for tabs other than the first tab (Driver) disappear after navigating
away and returning to the Custom Fields Manager.

Problem

• Custom fields display correctly for the first tab (Driver)
• Custom fields vanish for all other tabs (Vehicle, Contact, Vendor, Place, Fleet, Issue, Fuel Report)
• API calls return correct data but component state management fails
• TabNavigation enhanced objects couldn't be matched to original subjects

Solution

• Fix TabNavigation integration with enhanced tab objects
• Add cache restoration method for navigation persistence
• Simplify subject matching to use model property only
• Add force reload parameters for delete operations

Testing

• ✅ All tabs now load custom fields correctly on first visit
• ✅ Custom fields persist across navigation
• ✅ Tab switching works reliably
• ✅ Create/delete operations work on all tabs

Changes

• Enhanced #updateSubject method with better object matching
• Added restoreFromCache() method for cached data restoration
• Simplified onTabChange action with empty group checking
• Added force reload for delete operations

Fixes fleetbase/fleetops#173