RFC to rename kv pacakge

[MrAlias]

From recent feedback and from existing understanding, it is recognized that kv is not an ideal package name.

Names such as kv, global and standard can easily overlap with other packages in the language ecosystem.
Consider giving them more unique names to improve developer productivity. Users shouldn’t stress about importing the name package by constantly checking the import paths or shouldn’t have to rename imports because of an overlap.

Based on the function of this package it seems like an appropriate package especially since it makes an attempt to not use keyvalue, but it would be ideal if we can brainstorm improved names.

[Aneurysm9]

I can't really think of any better package names that don't suffer from the same potential issues.

[MrAlias]

Decision from the SIG meeting today was to got with #1052

[seh]

This is probably a better place to ask this question: #1052 (comment).