Cherry-pick #23886 to 7.11: [Elastic Agent] Fix issues with dynamic inputs and conditions

[blakerouse]

Cherry-pick of PR #23886 to 7.11 branch. Original message:

What does this PR do?

Fixes 2 issues that where affecting the usage of dynamic inputs and conditions.

• Loading of the configuration was not excluding the inputs from the go-ucfg variable expansion. Inside of inputs on variable expansion is done by the dynamic inputs code.
• EQL string methods where too strict on type checks, this lowers that to try to convert any type to a string before doing the comparison. This is important in cases where a variable results to an un-expected type, like *eql.null.

Why is it important?

Usage of dynamic inputs work as expected.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Closes [Ingest Manager]: Data Stream not generated for standalone Agent on kibana. #23829
• Closes [Agent] Dynamic inputs fail to get validated #23685

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[elasticmachine]

Pinging @elastic/agent (Team:Agent)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #24005 opened

• Start Time: 2021-02-11T14:52:50.184+0000

• Duration: 30 min 26 sec

• Commit: cacceef

Test stats 🧪

Test	Results
Failed	0
Passed	5654
Skipped	24
Total	5678

Trends 🧪

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	5654
Skipped	24
Total	5678