Mappings for Integration Inputs are not dynamic

[dikshachauhan-qasource]

While working upon adding support for windows integration in E2E scripts, we have found that current code is hard coded for Linux Integration and only maps one input for metrics data stream that it generates.

So, With the above approach, we are not able to use framework methods appropriatly for all other integrations validations.

Make them to refer to Kibana APIs directly to pick default integration template than static hard-coded values, as this would help to pick all the integration inputs. Please refer below screenshots to understand current behavior.

Screenshots:

• How Linux integration is currently added through existing code:
  

• How it is added on Kibana by default
  

• How other integrations are being added to policy right now without any inputs mapping
  

• Function where Linux mapping is hard-coded as of now:
  

cc @mdelapenya

[mdelapenya]

The system integration support was initially added by @IgorGuz2000, so I recommend pinging him once there is bandwidth to work on this issue