[Upgrade flow] Store user changes as modifications

[andresmgot]

Description:

When upgrading an app, if any modification is made to the values, changing the version will have no effect. This is because in the past, we didn't have a way to differentiate between user changes and version changes. Now since we store user modifications (in the deployed version), we can also store modifications that has not been submitted yet.

Steps to reproduce the issue:

1. Deploy an old version
2. Click upgrade
3. Change something in the values
4. Change the version

Describe the results you received:

After that, the step 4 has no effect.

Describe the results you expected:

In the step 4, the changes in the values from the new version should be applied.

Additional information you deem important (e.g. issue happens only occasionally):

Version of Helm, Kubeapps and Kubernetes:

• Output of helm list <kubeapps-release-name>:

NAME    	NAMESPACE	REVISION	UPDATED                                	STATUS  	CHART         	APP VERSION
kubeapps	kubeapps 	3       	2020-06-04 15:20:40.202571364 +0000 UTC	deployed	kubeapps-3.7.0	v1.10.1    

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ppbaena]

To be verified.

[ppbaena]

Closed as included in the new table view and editor (#4396) comparing default values, deployed values, and new values for the package.