state: add RavenDB support

[nmalocic]

Added files related to RavenDB implementation from old branch for cleaner history

Description

Added support for RavenDB as state store.
Support for Set, Get, Delete and Multi interfaces.
Added conformance and certification tests

Issue reference

Please reference the issue this PR will close: #3318

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]

[elena-kolevska]

Hey @nmalocic thank you for your contribution!
Can you please sign your commits and check the failing tests?
https://github.com/dapr/components-contrib/pull/3702/checks

[daixiang0]

@nmalocic could you use a more meaningful title?

[nmalocic]

@elena-kolevska Commit is signed and now I see pending conformance tests, is there anything to fix before they are runned?

@daixiang0 Is title better now, should I also update description?

[daixiang0]

@elena-kolevska Commit is signed and now I see pending conformance tests, is there anything to fix before they are runned?

@daixiang0 Is title better now, should I also update description?

Please remove issue number in the title, format as "state: add RavenDB support". Also update description.

[elena-kolevska]

Thanks Patrick!
There's a lint error preventing cert tests to run.
Also, I didn't see the ravendb conformance test in the executed actions, it needs to be added in there (I think in the .github/scripts/test-info.mjs file). Check this pr for reference: #3588

[elena-kolevska]

Overall looks good, just a few small things and also check the lint failures pls.
Great work!

[elena-kolevska]

We need to put this in a secret and get a license that never expires

[elena-kolevska]

This looks good to me and can be merged as soon as the licence key is removed from code and set as an env variable.

[cicoyle]

@nmalocic - mind running the linter locally and fixing the issues?

[nmalocic]

@yaron2 What would be next steps for this PR?

[nmalocic]

@cicoyle lint is fixed, what would be next steps for this PR?

[JoshVanL]

@nmalocic please could you resolve the conflict? 🙂

[nmalocic]

@nmalocic please could you resolve the conflict? 🙂

Hi @JoshVanL is it ok now?

[JoshVanL]

@nmalocic please could you resolve the conflict? 🙂

Hi @JoshVanL is it ok now?

Thanks, @nmalocic- let’s see what CI says
Appreciate your work on this!

[JoshVanL]

@nmalocic I think you need to run make modify-allor equivalent I this repo.

[nmalocic]

hi @JoshVanL I fixed few merges and ran modtidy. Is there a way that I can check all this checks locally?

[github-actions]

This pull request has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!