Local file-based name resolver with SQLite + Update components-contrib to register Blob Storage v2

[ItalyPaleAle]

Fixes #3256

This PR updates components-contrib to the latest commit, so it also requires registering the new Azure Blob Storage v2 components

Addresses a longstanding request (> 2 years!) to have an alternative name resolver component for local development, for situations where mDNS can't be used (and even in those situations, a local name resolver is more convenient for local development).

As discussed in dapr/components-contrib#1380, this is implemented with SQLite, which is fast and efficient.

[codecov]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (90835fa) 65.01% compared to head (44033e5) 65.07%.

❗ Current head 44033e5 differs from pull request most recent head 437cde1. Consider uploading reports for the commit 437cde1 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #7038      +/-   ##
==========================================
+ Coverage   65.01%   65.07%   +0.05%     
==========================================
  Files         221      231      +10     
  Lines       20799    21060     +261     
==========================================
+ Hits        13523    13704     +181     
- Misses       6138     6214      +76     
- Partials     1138     1142       +4     

Files	Coverage Δ
pkg/messaging/direct_messaging.go	55.63% <0.00%> (ø)
pkg/runtime/runtime.go	73.18% <86.36%> (+0.03%)	⬆️

... and 23 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[JoshVanL]

One thing, otherwise LGTM 👍

Could you add a simple service invocation integration test using SQLite?

[ItalyPaleAle]

The PR in contrib was merged so this is good to go!! 🚀

Could you add a simple service invocation integration test using SQLite?

No, we should not use tests in the runtime to validate a component. There are some “ITs” for this component in components-contrib (implemented as unit tests because we don’t have an infra to do otherwise). We should add an infra in components-contrib to test nameresolvers, also for the other nameresolvers that don’t have a test (Consul)

[ItalyPaleAle]

A small API change in contrib. Now properties such as address and port are passed in a strongly-typed struct rather than in a weakly-typed map.

Addressed

[yaron2]

Integration tests seem to be consistently failing. I reran the tests 3 times. Are there known issues in master branch with integration tests? cc @JoshVanL

[ItalyPaleAle]

Integration tests seem to be consistently failing. I reran the tests 3 times. Are there known issues in master branch with integration tests? cc @JoshVanL

Looks like the test that's failing is the reminders rebalancing, and it's failing consistently in this PR and also when I run it locally. It appears the issue is that placement table dissemination doesn't happen in time.

It's really weird as this PR doesn't touch anything related to placement 😮

I am investigating

[ItalyPaleAle]

The issue seems to be an unrelated bug introduced by a separate commit in components-contrib. I'm going to fix or revert that commit.

--EDIT Fixed