chipingress: add option to force IPV4

[pkcll]

What

• loop/server: wire up properly ChipIngressInsecureConnection option
• chipingress: add option for gRPC client to force IPv4 connections.
  This is needed to connect to the public Cloudflare endpoint when IPv6 is not enabled on the local client network stack.

Why

loop/server: wire up properly ChipIngressInsecureConnection option

In some cases chipingress and beholder gateway collector connections could have different setup for TLS (InsecureConnection option). E.g connecting to local collector sidecar might not need TLS while connecting to public chipingress domain does need TLS. For local development both do not need TLS.

chipingress: add option for gRPC client to force IPv4 connections.

Error

{"level":"info","ts":1755007389.045963,"caller":"beholder/dual_source_emitter.go:54","msg":"failed to emit to chip ingress:
rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp   
[2606:4700:10::ac42:aedd]:443: connect: network is unreachable"","version":"(devel)@unset"}

Error message explanation:

Client tries to connect to staging.telemetry.chain.link
The DNS resolver looks up the domain and gets back both IPv4 and IPv6 addresses from Cloudflare (IPv6 Compatibility flag is enabled by default on Cloudflare network settings and cant be disabled).
The OS decides to try the IPv6 address [2606:4700:10::ac42:aedd] first.
It seems the node network stack has no route to send IPv6 packets to the public internet, so it immediately fails with network is unreachable.

[pkcll]

Closing this PR, ChipIngressForceIPV4 is not needed for communicating to public Cloudflare ChIP ingress endpoint.
The issue was related to incorrectly set ChipIngressInsecureConnection introduced in this PR
https://github.com/smartcontractkit/chainlink-common/pull/1374/files

Opened new PR for ChipIngressInsecureConnection only
smartcontractkit/chainlink#18947