Gridbox 2.20 Editor Saving Failed in Joomla 5.4 Multi-language Environment (Session Token Desynchronization)

Hi Balbooa Team,

I run a professional web design studio and highly rely on Gridbox 2.20 for our clients' enterprise websites. Recently, I discovered a critical core bug in the Gridbox editor when working within Joomla's native multi-language environment.

### Issue Description:
When editing an associated multi-language page, switching languages using the top language switcher within the Gridbox editor interface causes the saving mechanism to break. Specifically, I can only save the page ONCE. Any subsequent attempts to save the page result in a "Save Failed" error, and the save button becomes completely locked/non-responsive.

This issue does NOT occur when editing a page in a single-language environment. It only triggers after using the built-in language switcher inside the editor grid.

### Root Cause Analysis for Your Devs:
1. Session Token Desynchronization: When Gridbox switches languages via an AJAX/partial refresh inside the editor, the Joomla Form/Session Token does not seem to desynchronize or refresh properly for the newly loaded language context. The second save attempt fails because Joomla core rejects the outdated/mismatched token as a security measure.
2. Database Check-out Lock: The multi-language associations (#__associations) or page state appears to remain in a "checked-out" status after the first save, locking subsequent database writes until a manual global check-in is performed.

### Steps to Reproduce:
1. Setup a Joomla 5 site with multi-language enabled (e.g., Traditional Chinese and English).
2. Create a Gridbox page and associate it with the other language.
3. Open the page in Gridbox Editor.
4. Use the Gridbox language switcher at the top to switch to the other language.
5. Make some changes and click "Save" (1st time -> Success).
6. Make another change immediately and click "Save" again (2nd time -> Fails / Saving Locked).

### My 无懈可击 (Flawless) Environment Specs:
To save your team time from standard debugging protocols, I have already fully optimized the server and database infrastructure. This is NOT a hosting or collation issue:
- Joomla Version: Joomla 5.4.6 Stable
- Gridbox Version: Gridbox 2.20.0.2
- PHP Version: 8.2.30
- Web Server: nginx/1.27.4
- Database: MariaDB 10.11.16
- Database Collation: Both the Database default collation and ALL tables are strictly set to [utf8mb4_unicode_ci]. There are no encoding conflicts.
- PHP Settings: max_input_vars = 5000, memory_limit = 512M, post_max_size = 128M.

Currently, this bug severely disrupts our B2B workflow, forcing us to open separate browser tabs for each language as a workaround.

Could your development team please investigate how Gridbox handles the AJAX Form Token exchange during language switching in Joomla 5.4, and implement a permanent fix in the next release?

Thank you for your excellent extension and continuous support!

Best regards,
James