feat(helm-chart): ability to set hostNetwork for lifecycle operator deployment

[JLont]

Description

This PR adds the ability to set the .spec.template.spec.hostNetwork value for the lifecycle-operator deployment in the helm-chart values. By default it will be set to false.

This is required due to the webhook being blocked while using Cilium on managed Amazon EKS clusters. This makes it so other deployments won't be able to deploy on our clusters.

How to test

Added the default values to .github/scripts/.helm-tests.

Checklist

• My PR fulfills the Definition of Done of the corresponding issue and not more (or parts if the issue is separated
  into multiple PRs)
• I used descriptive commit messages to help reviewers understand my thought process
• I signed off all my commits according to the Developer Certificate of Origin (DCO)
  see Contribution Guide
• My PR title is formatted according to the semantic PR conventions described in
  the Contribution Guide
• My code follows the style guidelines of this project (golangci-lint passes, YAMLLint passes)
• I regenerated the auto-generated docs for Helm and the CRD documentation (if applicable)
• I have performed a self-review of my code
• I have made corresponding changes to the documentation (if needed)
• My changes result in all-green PR checks (first-time contributors need to ask a maintainer to approve their test runs)
• New and existing unit and integration tests pass locally with my changes

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.36%. Comparing base (e048679) to head (e312efc).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3500   +/-   ##
=======================================
  Coverage   85.36%   85.36%           
=======================================
  Files         167      167           
  Lines        7412     7412           
=======================================
  Hits         6327     6327           
+ Misses        798      797    -1     
- Partials      287      288    +1     

see 3 files with indirect coverage changes

Flag	Coverage Δ
certificate-operator	69.23% <ø> (ø)
component-tests	58.77% <ø> (ø)
lifecycle-operator	83.46% <ø> (ø)
metrics-operator	88.32% <ø> (ø)
scheduler	34.74% <ø> (ø)

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

[odubajDT]

Let's try to add the parameter also to the Deployment here with default value false

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[odubajDT]

Thank you for contribution! :)