fix(badger): Add missing SamplingStoreFactory.CreateLock method

[slayer321]

Which problem is this PR solving?

• Resolves [Bug]: badger as sampling store not work #4963

Description of the changes

• Implement missing CreateLock method on SamplingStoreFactory interface for badger

How was this change tested?

• run the Integration and make test command

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: yarn lint and yarn test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (076cd87) 95.59% compared to head (5f7fe8f) 95.60%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4966      +/-   ##
==========================================
+ Coverage   95.59%   95.60%   +0.01%     
==========================================
  Files         317      318       +1     
  Lines       18689    18695       +6     
==========================================
+ Hits        17866    17874       +8     
+ Misses        661      659       -2     
  Partials      162      162              

Flag	Coverage Δ
cassandra-3.x	25.64% <ø> (ø)
cassandra-4.x	25.64% <ø> (ø)
elasticsearch-5.x	19.91% <ø> (ø)
elasticsearch-6.x	19.91% <ø> (ø)
elasticsearch-7.x	20.05% <ø> (ø)
elasticsearch-8.x	20.12% <ø> (-0.02%)	⬇️
grpc-badger	19.53% <0.00%> (-0.02%)	⬇️
kafka	14.07% <ø> (ø)
opensearch-1.x	20.05% <ø> (ø)
opensearch-2.x	20.05% <ø> (+0.01%)	⬆️
unittests	93.36% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[yurishkuro]

@slayer321 this issue should've been caught at compile time, and via integration test, but it looks like this PR is not changing any of those. The storage factory must implement this interface

jaeger/storage/factory.go

Line 54 in 47f39a8

type SamplingStoreFactory interface {

I think the issue with integration tests is that the StorageIntegration struct is defined with direct access to SpanWriter etc. that are pre-initialized by the concrete implementation. Instead it would be better if implementations would only initialize the respective factories and let the test retrieve writer, etc. (we could do it in another PR).

[yurishkuro]

Cf: #4967

[yurishkuro]

Thanks!