[db] KvWithVersion to handle both versioned and non-versioned namespace

[dustinxie]

Description

as title.
based on (#4517)

Type of change

Please delete options that are not relevant.

• [] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• [] Code refactor or improvement
• [] Breaking change (fix or feature that would cause a new or changed behavior of existing functionality)
• [] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• make test
• [] fullsync
• [] Other test (please specify)

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• [] My code follows the style guidelines of this project
• [] I have performed a self-review of my code
• [] I have commented my code, particularly in hard-to-understand areas
• [] I have made corresponding changes to the documentation
• [] My changes generate no new warnings
• [] I have added tests that prove my fix is effective or that my feature works
• [] New and existing unit tests pass locally with my changes
• [] Any dependent changes have been merged and published in downstream modules

[sonarcloud]

Quality Gate failed

Failed conditions
36.5% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[envestcc]

Using kvBase in kvWithVersion is strange, I would recommend splitting it up. for example:

KvVersioned interface{
    Version(string, []byte) (uint64, error)
    SetVersion(uint64) KVStore
    Plain() KVStore
}

[dustinxie]

do you mean add a Plain() interface?
this is internal implementation, for non-versioned namespace, it is a regular Put/Get/Delete, same as now