Bump kine to v0.13.10 (to fix a bug introduced in v0.13.4)

[svanharmelen]

Description

Kine v0.13.4 introduced a small bug which we hit when updating to k0s version v1.32.1+k0s.0 (and made us revert the update for now). The main issue and the fix is described in this PR which is included in the latest release (v0.13.10): k3s-io/kine#414

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

How Has This Been Tested?

• Manual test
• Auto test added

Checklist

• My code follows the style guidelines of this project
• My commit messages are signed-off
• I have performed a self-review of my own 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
• I have checked my code and corrected any misspellings

[twz123]

Thanks 🚀

[k0s-bot]

Successfully created backport PR for release-1.32:

• [Backport release-1.32] Bump kine to v0.13.10 (to fix a bug introduced in v0.13.4) #5595

[svanharmelen]

Thanks for merging the PR @twz123! Do you have any (rough) idea when a new release will be made which will include this fix? We temperately rolled back some of our changes (which included the k0s release) so are looking forward to be able to rollout the changes again using an updated version of k0s. Thanks!