fix: cve bump from v0.0.5 to v0.0.6

[saikumar98419]

What problem does this PR solve?:

Which issue(s) does this PR fix?:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Checklist

• If the PR adds a version bump, ensure there is no breaking change in Licensing model (or NA).
• If a chart is changed or app configuration is significantly changed, the chart version is correctly incremented (so that apps are not automatically upgraded from a previous version of DKP).

[github-actions]

✅ Created Kommander branch to test kommander-applications changes: https://github.com/mesosphere/kommander/tree/kapps/main/cve-bump-v0.0.6

[coveralls]

Pull Request Test Coverage Report for Build 11659418298

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 51.703%

---

Totals
Change from base Build 11582457332:	0.0%
Covered Lines:	167
Relevant Lines:	323

---

💛 - Coveralls

[mhrabovcin]

We need to bump the service version from 4.2.5 to 4.2.6 and all references in the service file.

[github-actions]

✅ Created Kommander branch to test kommander-applications changes: https://github.com/mesosphere/kommander/tree/kapps/main/cve-bump-v0.0.6

[SandhyaRavi2403]

@mhrabovcin,

The above 2 commits are not signed. Is it fine or should a new PR be raised ?