XIVY-19301 Persist useOnFocus value on unmount

[ivy-edp]

When switching tabs quickly when inside a SingleLineCodeEditor, the blur event is not fired before the component unmounts. As a result, the most recently typed value is being lost.

This change adds an unmount cleanup to useOnFocus that calls onChange with the latest focused value. This ensures edits are persisted even when blur is skipped.

I am not sure if this is the best approach, as now the onChange is also always triggered on mount of the component too, which is not nessacary. Maybe i can add a check that ensures the onChange only runs if the value actually changed. There may also be a cleaner solution that avoids this behavior altogether.

If this approach looks reasonable, I can also add a test covering this scenario.

[ivy-lli]

No idea either... Has AI proposed this?
A test for it would definitely be cool :)
But I think this is the same bug as: https://axon-ivy.atlassian.net/browse/XIVY-19187?

[Copilot]

Pull request overview

This PR addresses a UX/data-loss issue where rapid tab switching can unmount a focused SingleLineCodeEditor before blur fires, causing the latest edits to be dropped. It adds an unmount-time persistence mechanism to useOnFocus so the last focused value is committed even when blur is skipped.

Changes:

• Add an unmount cleanup in useOnFocus intended to persist the latest focused value via onChange.
• Track latest value/callback via refs so the cleanup uses up-to-date data.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ivy-edp]

No idea either... Has AI proposed this? A test for it would definitely be cool :) But I think this is the same bug as: https://axon-ivy.atlassian.net/browse/XIVY-19187?

Yes AI proposed it and I quickly check and it seems to work with no side effect ✌️
I will add a test 👍
Yes this probably will also fix the bug you mentions or at least the process-editor part. I would need to check the form-editor separatly