Refactor 'unsaved changes' modal to use KModal component and update tests

[Kartikayy007]

Summary

Replaced Vuetify's MessageDialog component with Kolibri Design System's KModal for the unsaved changes dialog in the Collections modal.

• Replaced MessageDialog with KModal in ChannelSetModal.vue
• Updated modal props to use KModal's API (title, submitText, cancelText)
• Maintained all existing functionality and event handlers

Manual verification:

1. Logged in as [email protected] with password a
2. Navigated to Channels > Collections
3. Clicked "New collection" button
4. Added text to Collection name input
5. Clicked close button in the top bar
6. Verified unsaved changes modal appears with KModal styling
7. Tested both "Exit without saving" and "Save and close" buttons
8. All functionality works as expected

References

• Fixes [Remove Vuetify from Studio] 'Unsaved changes' modal in Channels - New collection #5299

Reviewer Guidance

Test these changes by:

1. Login as [email protected] with password a
2. Go to Channels > Collections
3. Click "New collection" button
4. Add text to Collection name input
5. Click the close button in the top bar
6. Verify the unsaved changes modal appears and functions correctly
7. Test both cancel and save actions

Areas to focus on:

• Modal properly blocks navigation when unsaved changes exist
• Both RTL and LTR layouts work correctly
• All 19 tests in channelSetModal.spec.js pass

[MisRob]

Thank you @Kartikayy007, we will assign a reviewer next week.

[LianaHarris360]

There just a few items that need to be cleaned up, but otherwise these changes are looking good, thank you @Kartikayy007!

[LianaHarris360]

We don't have to import KModal from KDS, this line can be removed :)

[LianaHarris360]

Likewise, this line should be removed, we don't need to insert KModal as a child component.

[LianaHarris360]

showUnsavedDialog is set to false within this.close(), which is called in this function already, so we don't need this line added here.

[MisRob]

@Kartikayy007 are you planning to resolve feedback?

[MisRob]

@LianaHarris360 since we didn't hear from @Kartikayy007, noting that @vtushar06 may finish this work in this PR, so that you don't need to review everything again - as suggested here.

[MisRob]

Closing in favor of #5432