feat(fqdn): Deduplicate and sort ExecTemplate output. Add functions

[ivankatliarchuk]

What does it do ?

• Make sure FQDN templating only output unique values, to reduce deduplication efforts downstream
• Adds a fromJson template function that decodes a JSON string into a Go value (map, slice, etc.) - Enables FQDN templates to work with structured data stored as JSON strings in ConfigMap data fields. For example, a ConfigMap can hold a JSON array of DNS entries, and templates can range over them to generate hostnames:
  {{ range $entry := (index .Data "entries" | fromJson) }}{{ index $entry "dns" }},{{ end }}
• Adds a hasKey template function that checks whether a key exists in a map[string]string. There is no other way to find where label is empty value is set on resourse - Go templates' built-in index returns the zero value ("") for missing keys, which is indistinguishable from keys with empty values. Kubernetes uses empty-value labels
  as markers (e.g. service.kubernetes.io/headless: ""), so templates need explicit key existence checking to conditionally generate hostnames based on label presence

Motivation

Templates can produce duplicate hostnames (e.g. multiple template expressions resolving to the same FQDN, or combineFQDNAnnotation merging overlapping results). Duplicates cause unnecessary DNS record creation attempts and then deduplications. Sorting ensures deterministic output, preventing spurious diff aka ExecTemplate returns ["b.com", "a.com"] one reconciliation and ["a.com", "b.com"] the next

slicing PR #6172

More

• Yes, this PR title follows Conventional Commits
• Yes, I added unit tests
• Yes, I updated end user documentation accordingly

[coveralls]

Pull Request Test Coverage Report for Build 21979665241

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.02%) to 79.174%

---

Totals
Change from base Build 21559764040:	0.02%
Covered Lines:	16051
Relevant Lines:	20273

---

💛 - Coveralls

[ivankatliarchuk]

/retitle feat(fqdn): Deduplicate and sort ExecTemplate output. Add functions

[vflaux]

/lgtm

[ivankatliarchuk]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ivankatliarchuk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [ivankatliarchuk]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment