Add a 'key-value system' component to the core project node so that issues can be filed against it and searched

+1 from me - it's a coherent core component so makes sense to have its own spot in the list.

So all for adding this component. More components means its easier to organize and hopefully from the subsystem standpoint easier to cover.

Would like to see a section added to MAINTAINERS.txt should we ask for volunteers?

@xjm pointed out out that if we add this, it should also include State and TempStore since both depend on KeyValue.

I've worked on KeyValue and State a long time ago so would put my name in MAINTAINERS.txt, although would be good to have at least one co-maintainer.

I am not entirely sure how to represent that in a component name though. Back to needs review for that.

Maybe just call if KV / State / TempStore ?

Since I've worked on this, especially for MongoDB, I might help co-maintaining it.

Moving to a plan.

Updated the issue summary.

I would prefer something simpler than. "KV / State / TempStore". I think it is sufficient to use 'key/value system' since that includes the other two. In a sense, it is a way to expose that dependency.