Two changes in this:
1. Remove the reviewers. These are from when Helm was under
Kubernetes and used its tools. That is no longer the case
so this section has no use.
2. List fibonacci1729 with the maintainers. He has been a
maintainer a long time. The original listing had to do with
department locations within Deis rather than his work. He
has been a maintainer since before Helm was a CNCF project.
Fixes#5685
Signed-off-by: Matt Farina <matt@mattfarina.com>

The other Kubernetes dependencies, such as client-go and apimachinery,
are pinned to 1.14.1 but Kubernetes itself was tracking the tip of the
1.14 release branch and picking up changes between releases. This
change pins Kubernetes to the same version as the other parts of it.
Signed-off-by: Matt Farina <matt@mattfarina.com>

Note, he has been emailed regarding the move including an offer to
re-engage. He has not taken this up. The governance has a 3 months
of inactivity clause that causes maintainers to fall off. This
period has been long exceeded per metrics measured in devstats.
Signed-off-by: Matt Farina <matt@mattfarina.com>

When Helm is packaging up the bundles it generates the checksums
but does not display them. Having them here will aide in the
generation of release notes and provide another source
listing them.
Signed-off-by: Matt Farina <matt@mattfarina.com>

Between grpc 1.2.x and 1.7.x there was an API change. The
previous MaxMsgSize is now a wrapper around MaxRecvMsgSize. This
change now sets the MaxRecvMsgSize and MaxSendMsgSize which need
to be set independently.

CRDs and other objects seen as unstructured cannot use strategic
merge patching. It has never been supported on CRDs. Previously,
cases like unstructured objects could have caused an unregistered
error. This is no longer the case.
This change explicitly looks for unstructured objects and handles
those using json merge patching.
Closes#3382