loop/server: wire up ChipIngressInsecureConnection option

[pkcll]

loop/server: wire up ChipIngressInsecureConnection option

Why?

ChipIngress should use TLS by default, while Beholder does not use TLS for local connection to sidecar collector by default.

Related PR #1374 cc @krehermann @Tofel

Testing

Companion PR smartcontractkit/chainlink#18947
Was tested on staging on cl-keystone-one

[github-actions]

apidiff results - no incompatible changes detected ✅

Module: github-com-smartcontractkit-chainlink-common

Status: ✅ 1 compatible changes

(Full summary: https://github.com/smartcontractkit/chainlink-common/actions/runs/17108988323/#summary-48525301974)

[patrickhuie19]

We have a variety of config parameters like this now (TLS or local mode), and I think some are formatted as secure while others are formatted as insecure. insecure is probably the way to go, so no action here.

[krehermann]

this will break the local env. please update all the relevant tomls like

https://github.com/smartcontractkit/chainlink/blob/cec7743de3e74839ce92f236146ce9e320a4a076/core/scripts/cre/environment/configs/workflow-don.toml#L74

ie review all the toml artifacts in that dir and add your new config val as appropriate

[pkcll]

this will break the local env. please update all the relevant tomls like

https://github.com/smartcontractkit/chainlink/blob/cec7743de3e74839ce92f236146ce9e320a4a076/core/scripts/cre/environment/configs/workflow-don.toml#L74

ie review all the toml artifacts in that dir and add your new config val as appropriate

@krehermann, pease see the note in the PR description "Companion PR smartcontractkit/chainlink#18947"
I believe Its done there.