Feature/#2017 editor

[jrobinAV]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

When locking a data node, providing an "editor_id" only prevents another editor from locking the data node; it does not prevent the other editor from writing the data node.

According to the documentation, it should prevent another editor from writing (appending, uploading) the data node.

Related Tickets & Documents

• Related Issue [🐛 BUG] Data node's editor id mechanism does not work  #2017
• Taking over PR Enforce Editor Lock for Write, Append, and Upload Operations in DataNode #2122, abandoned by the contributor.

Checklist

• Does this solution meet the acceptance criteria of the related issue?
• Is the related issue checklist completed?
• Does this PR add unit tests for the developed code?
• Was the documentation updated, or a dedicated issue for documentation created?

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
19363	16889	87%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
taipy/core/data/_file_datanode_mixin.py	98%	🟢
taipy/core/data/data_node.py	99%	🟢
taipy/gui_core/_context.py	63%	🟢
TOTAL	87%	🟢

updated for commit: 936b600 by action🐍