test: unit test for CardTemplateEditor

[criticalAY]

Purpose / Description

When a user attempted to save changes in the CardTemplateEditor, the save button was typically disabled to prevent double-submissions. However, if an unexpected exception occurs during the save logic, the button remained disabled, forcing the user to restart the activity. This change adds a regression test to ensure the button is always restored to an enabled state regardless of success or failure. resolves a TODO from my previous PR

Fixes

NA

Approach

NA

How Has This Been Tested?

Local test

Learning (optional, can help others)

NA

Checklist

Please, go through these checks before submitting the PR.

• 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]

I don't like requesting changes on test code, hopefully less frustrating as this is a patch 😅

[david-allison]

If feasible, we should confirm that an error occurs, this informs us if someone 'breaks' the test by 'breaking' the failure simulation of:

        // throw an exception to simulate failure
        testEditor.tempNoteType = null

[criticalAY]

I tried multiple ways the error is there but since we are throwing it the test fails due the reason I stated I would leave it for now, we can create more tests later for now something is better than nothing

[david-allison]

Sure, I didn't expect much effort to be put here, if it's not easy we can come back to it later

[lukstbit]

I fixed the conflict to move things forward.

I kept the original code, we use binding now but as this uses a menu item I didn't want to complicate things(we are also currently modifying this screen so the tests might be changed as well).