Ensure latest notetype data is used after updates

[ShridharGoel]

Purpose / Description

Ensure latest notetype data is used after updates. This is done to fix an issue where old notes name was still showing while creating a card after updating a note type's name.

Fixes

• Fixes Renaming note types requires a restart #18394

Approach

The bug occurred because when a notetype was renamed via updateNotetype(), the old cached version with the original name remained in memory, causing UI components to show stale data until app restart.

With this new approach:

• removeFromCache(specificId) removes the updated notetype from cache.
• Next access to that notetype fetches fresh data from backend with new name.

How Has This Been Tested?

Manual testing + unit test.

Screen_recording_20250531_170034.webm

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner

[david-allison]

Love the tests, thanks so much!

[mikehardy]

LGTM