DYN-9707 : Show warning when a file is opened in another Dynamo instance

[ivaylo-matov]

Purpose

This PR addresses DYN-9707:

The proposed logic adds a graph-file locking mechanism so Dynamo can detect when a .dyn or .dyf file is already open in another Dynamo instance and help avoid conflicting edits.

Changes:

• added core graph lock sidecar support using .dynlock files.
• added lock acquisition, heartbeat refresh, stale-lock takeover, and release behavior.
• integrated graph locking into DynamoModel.OpenFileFromPath.
• added WPF conflict prompt with Cancel and Save As options.
• added localized prompt resources and PublicAPI entries for new resource strings.
• updated the open-file UI flow to handle cancelled opens and Save As copy redirects.
• added regression tests for lock creation/release, stale lock takeover, Cancel, and Save As prompt outcomes.

Declarations

Check these if you believe they are true

• Is documented according to the standards
• The level of testing this PR includes is appropriate
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.

Release Notes

Dynamo now warns before opening a graph already open in another instance.

Reviewers

@DynamoDS/eidos
@jasonstratton

FYIs

@dnenov
@johnpierson

[github-actions]

See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-9707

[jasonstratton]

We discussed in the check-in today the possibility of orphaned lock files. The logic still seems sound. We discussed the length of the timeout of 90 seconds being reasonable, which I think it is, but there is an edge case to consider.

If the user has two instances of Dynamo open with a file open in one of them and Dynamo crashes, it is conceivable that the user could switch to the other instance and try to open the file, which now had an orphaned lock file, fairly quickly and well under the 90 seconds.

It's probably a rare case, but it would be confusing if a user runs into it as the two options presented are to cancel opening the file and to create a copy of the file. It might merit some sort of text that explains this possibility? It might be overly verbose and almost never relevant though.

@johnpierson , what do you think?

[jasonstratton]

I had a couple of comments, but only one code change needed.

Great work! Thank you.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jasonstratton]

Thank you!

[ivaylo-matov]

Thank you!

Thanks you @jasonstratton

I pushed a follow-up PR here #17153.

[jasonstratton]

I pushed a follow-up PR here #17153.

Thank you @ivaylo-matov . I did see the PR. Is it ready to review? ... I suppose I should ask there. 😄

[johnpierson]

I actually ran into the "orphaned dynlock" file myself when testing another issue that resulted in a hard crash.