Adding a max helm history field for k8sservice

[juandiegopalomino]

Description

Cause a problem Will was facing is that he made hundreds of deployments and so the history was obscenely large

Safety checklist

• This change is backwards compatible and safe to apply by existing users
• This change will NOT lead to data loss
• This change will NOT lead to downtime who already has an env/service setup

How has this change been tested, beside unit tests?

YOUR_ANSWER

[codecov]

Codecov Report

Merging #835 (8d7a8cb) into main (1091f58) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #835   +/-   ##
=======================================
  Coverage   74.06%   74.06%           
=======================================
  Files         119      119           
  Lines        7821     7821           
=======================================
  Hits         5793     5793           
  Misses       2028     2028           

Flag	Coverage Δ
unittests	74.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1091f58...8d7a8cb. Read the comment docs.

[bigbitbus]

why should this be a configurable parameter? Are there too many history entries for a customer?

Why not set default to 0 (infinite)? Its not problemmatic for most people, and gives them all their history...

[nsarupr]

Should we keep the default value for max_history as 0, the same as terraform does?