[WIP] Create a file-based lockstore component

[moonorange]

Description

Please explain the changes you've made

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #[issue number]

Related PR and discussion

dapr/dapr#7631 (comment)

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

[moonorange]

Hi, @elena-kolevska
I'd appreciate your early feedback to ensure I'm on the right track.
I am implementing an in-memory lock store similar to
https://github.com/dapr/components-contrib/blob/main/state/in-memory/in_memory.go.

Should I continue with this approach, or should I use files similar to
https://github.com/dapr/components-contrib/blob/main/secretstores/local/file/filestore.go ?

[elena-kolevska]

Hi @moonorange , I'm happy to see your work on this!
Due to the nature of what we're trying to do here, a file-based lock will make more sense because it can be accessed by multiple applications.

[berndverst]

I am one of the maintainers of this repository and I have no context for what this PR is about or which issue it is addressing.

Please first create a new issue in dapr/components-contrib that explains what feature or functionality is needed and why.

[moonorange]

Hi @berndverst, I created a new issue for this PR
#3438

[yaron2]

@moonorange we are approaching code freeze, it'd be great if you got the PR ready for review this week. Thanks!

[yaron2]

Ping @moonorange