fix: feat(node-analyzer,cluster-scanner): resolving bug with nodeAnalyzer and clusterScanner condition.

[IgorEulalio]

What this PR does / why we need it:

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• [ x ] Title of the PR starts with type and scope, (e.g. feat(agent,node-analyzer,sysdig-deploy):)
• [ x ] Chart Version bumped for the respective charts
• [ x ] Variables are documented in the README.md (or README.tpl in some charts)
• [ x ] Check GithubAction checks (like lint) to avoid merge-check stoppers
• [ x ] All test files are added in the tests folder of their respective chart and have a "_test" suffix

Check Contribution guidelines in README.md for more insight.

[IgorEulalio]

We found that the validation was having issues when executing it with helm version 3.9.3.

The mechanism to validate wether or not runtimeScanner or clusterScanner was improved to guarantee nested object validation before accessing it.

Two new unit tests were introduced to make sure deployments without nested objects (nodeAnalyzer and nodeAnalyzer.runtimeScanner) work properly.

Cc: @AlbertoBarba