Feature: a view is saved as a project that agents edit live #49

Problem

• A view can only be exported as a script (export_script, export_changes); there is no file the window saves to and opens again
• A person in the window and a coding agent in the code can not work on one setup: changes of one never reach the other
• Several people can not work on one setup at the same time, e.g. from a shared drive

Proposal

A view is saved as a project of BeamletOpticsProjects: a folder with the setup as readable code, own code and the pinned package versions, opened by its .bmo file. The open window writes every finished action to the files and takes in what agents or other people write there, without a reload; when the window and the files changed the same object differently, the person decides. Everyone on the project, person or agent, is shown at what they work on. Versions are saved on request, without a git install.

gui = open_project("Bench/Bench.bmo")

Tasks

• A view is saved to and opened from a project folder, also with "Save as" and by its .bmo file
• Every finished action in the window is in the files without pressing a key
• What an agent writes to the files appears in the open window without a reload
• An object changed differently in the window and in the files is shown as a conflict to decide
• Other people and agents on the project are shown at their selection, also over a shared drive
• Ctrl+S saves a version, Ctrl+R takes the files as they are
• Groups made in the window are kept in the project
• Live view docs: a section on projects

Notes

• Builds on BeamletOpticsProjects (https://github.com/StackEnjoyer/BeamletOpticsProjects.jl), not registered yet
• Implemented in Feature: projects with live sync, selections of several, groups #48; grouping itself is Feature: Selected objects are made a group in the window #40 / Feature: Ctrl+G groups, rectangle selection, group pivot #45
• Out of scope: claims (locks) so that two people do not edit the same object, a separate issue