Fix normalizers to not parse list values if they are already parsed

[awahab07]

Fixes #133212

Summary

While configuring a Synthetics Integration via yaml, the list values (e.g. ssl.supported_protocols under TLS Configuration of HTTP monitor or tags for any monitor) are re-parsed via JSON.parse when they were already parsed and converted to a JS Array by js-yaml, causing the following error on Synthetics Integration Edit Page:

This PR fixes this and before applying JSON.parse, first checks if the value is already parsed.

How to test

• Connect local Kibana to a cluster with Fleet Server installed e.g. edge-oblt cluster
• In kibana.dev.yml, put the following Synthetics Integration config

xpack.fleet.agentPolicies:
  - name: Synthetics Agent Policy Test - Issue
    id: synthetics-agent-policy-test-issue
    namespace: default
    package_policies:
      - name: synthetics-test1
        package:
          name: synthetics
        id: my-monitor-test1
        inputs:
          - type: synthetics/http
            enabled: true
            streams:
              - data_stream:
                  type: synthetics
                  dataset: http
                enabled: true
                vars:
                  - name: type
                    value: http
                  - name: urls
                    value: 'http://www.httpvshttps.com/'
                  - name: schedule
                    value: '"@every 5m"'
                  - name: ssl.verification_mode
                    value: none
                  - name: ssl.supported_protocols
                    value:
                      - TLSv1.1
                      - TLSv1.2
                      - TLSv1.3
                  - name: tags
                    value:
                      - test1
                      - test2
                      - test3
                      - test4

• Goto Management -> Fleet -> Synthetics Agent Policy Test - Issue -> synthetics-test1
• You shouldn't see the above error

---

Note: There's an issue with the UI that on editing a yaml configured integration, the Tags or Supported TLS protocols combobox shows invalid state with "elastic" as an option value. As shown below:

Turned out it is the browser autofill which puts "elastic" as the default value. The default value "elastic" comes from Kibana's username input field as both input fields (the username and the one contained within EuiComoBox component) are unnamed. Eui team has been informed about this as there should be an option to set autocomplete="off" on EuiComboBox component.

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[awahab07]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: dafc1dc
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
synthetics	848	849	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
synthetics	858.1KB	858.1KB	+28.0B

History

• 💚 Build #49190 succeeded 65b78e7

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[shahzad31]

Tested it and it works as expected now !!

[kibanamachine]

💚 All backports created successfully

Status	Branch	Result
✅	8.3

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation