[0.9] Honor Helm's MaxHistory when using drift correction

[aruiz14]

Refers to #2515

• Drift correction (self-healing) uses Helm's Rollback action, which has a MaxHistory field. This value takes precedence over the config value. Unlike the Upgrade action, we omitted to set this value, so the releases will only shrink when running an upgrade but not rollbacks`.
• I noticed that sometimes, a regular upgrades would be deployed (creating a new). Initially I thought this would happen if all the releases in the remaining history were rollbacks, but realized the problem is that the BundleDeployment status has a release field, referencing the latest release installed. This value is not being updated on rollbacks, hence making the status differ from what helm history reflects.

[weyfonk]

Thanks for troubleshooting and fixing this bug :)
Ideally we'd have tests for this, which in this case most likely mean end-to-end tests.