Osquerybeat: Add support for input/integration level osquery platform/version/discovery configuration

[aleksmaus]

What does this PR do?

Add support for input/integration level osquery platform/version/discovery configuration.
This allows to map the integration configuration to the osquery packs 1:1.
The platform and version constraints at the input level had to have a different name currently in order to avoid these values to be injected in every stream instead, that's why the names are iplatform and iversion as abbreviation for the input platform and the input version.

This change requires the updated osquery_manager integration elastic/integrations#1441
and is also couple of more fixes on kibana side:

1. kibana needs to be able to create integration configuration with empty vars, currently it returns error when you try to add updated osquery_manager integration into the policy.
2. the configuration page for osquery maanger needs to remove compiled_input from the payload from the input request payload when updating the integrations configurations

This change can be merged before the work mentioned above, the new constraints just would get propagated with the the policy and would not apply to the osquery configuration without those changes.

Here is an example of the request payload with the new constraints:

{
    "name": "osquery_manager-1",
    "description": "",
    "policy_id": "548a3940-df4e-11eb-8fdd-b98cebb63257",
    "namespace": "default",
    "inputs": [
        {
            "type": "osquery",
            "enabled": true,
            "streams": [
                {
                    "data_stream": {
                        "type": "logs",
                        "dataset": "osquery_manager.result"
                    },
                    "id": "osquery-osquery_manager.result-ce361ed0-559c-4549-a71c-c48dd64a12d3",
                    "vars": {
                        "query": {
                            "type": "text",
                            "value": "select * from users limit 5"
                        },
                        "interval": {
                            "type": "integer",
                            "value": "60"
                        },
                        "id": {
                            "type": "text",
                            "value": "users"
                        }
                    },
                    "enabled": true
                }
            ],
            "policy_template": "osquery_manager",
            "vars": {
                "iplatform": {
                    "type": "text",
                    "value": "posix"
                },
                "discovery": {
                    "type": "text",
                    "value": [
                        "SELECT pid FROM processes WHERE name = 'osquerybeat';",
                        "SELECT 1 FROM users WHERE username like 'amau%';"
                    ]
                },
                "iversion": {
                    "type": "text",
                    "value": "4.7.0"
                }
            }
        }
    ],
    "enabled": true,
    "output_id": "",
    "package": {
        "name": "osquery_manager",
        "title": "Osquery Manager",
        "version": "0.5.1"
    }
}

Here is the screenshot of the policy configuration with the new input level constraints

Why is it important?

This is needed in order to support the osquery packs further configuration options.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• have added tests that prove my fix is effective or that my feature works

Related issues

• Requires Osquery_manager: Input level settings for platform and version osquery pack constraint integrations#1441

Special thanks to @nchaulet for working with me yesterday through undocumented obstacles of integration package changes and kibana errors.

[botelastic]

This pull request doesn't have a Team:<team> label.

[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

• Start Time: 2021-08-04T14:03:40.624+0000

• Duration: 52 min 4 sec

• Commit: 41e8f66

Test stats 🧪

Test	Results
Failed	0
Passed	3656
Skipped	0
Total	3656

Trends 🧪

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test	Results
Failed	0
Passed	3656
Skipped	0
Total	3656