feat: LockFileEx/UnLockFileEx methods shouldn't be called explicitly

[Jklawreszuk]

PR Details

Stride should avoid direct references to any OS if possible. This PR Hides Lock/UnLockEx methods under already made Lock/Unlock methods that wrap them.

Related Issue

None, but this relates to Stride.Launcher which is using FileLock.Wait method, so this provides cross-platform experience

Types of changes

• Docs change / refactoring / dependency upgrade
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change - kind of, but only changes return type from void --> bool

Checklist

• My change requires a change to the documentation.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have built and run the editor to try this change out.

[Eideren]

Should this be renamed to TryLockFile instead ?

[Jklawreszuk]

@Eideren Huh...Your're right, It should 😅 I have now added your suggestion

[Jklawreszuk]

oh,yea...I forgot the parentheses. This is the last fix I promise 😆

[Jklawreszuk]

Sorry, I should have just built it myself straight away before sending the PR 🤐 . I've built the project so the test should pass

[Eideren]

Thanks !