feat: (PSKD-957) ingress-nginx configmap changes for v1.12+

[dhoucgitter]

Changes

• Add one or two config map values as required to maintain the default values they had prior to ingress-nginx v1.12
• ingress-nginx v1.12.0 has changed the defaults for those two config map values, the values required by the Viya platform differ from the new defaults.

Tests

A set of the tests below will be spot checked when the ingress-nginx v1.12.0 helm chart is available and updated in the related internal ticket for that purpose.

Development tests

Scenario	Provider	K8s version	ingress-nginx chart version	Cadence	relevant ingress-nginx config map values set	Notes
1	Azure	1.30	4.11.1	stable:2024.11	None	No additional cm value set for 2024.11 cadence
2	Azure	1.30	4.11.1	stable:2024.08	None	No additional cm value set for 2024.08 cadence
3	Azure	1.30	4.11.1	stable:2024.12	None	No additional cm value set for 2024.12 cadence
4	Azure	1.30	4.11.1	fast:2020	None	No additional cm value set for fast:2020 cadence
5	Azure	1.30	4.11.1	lts:2024.03	None	No additional cm value set for lts:2024.03 cadence
6	Azure	1.30	4.11.3 *	lts:2024.03	strict-validate-path-type: 'false';annotations-risk-level: Critical	Expected 2 cm values set for lts:2024.03 cadence and stand-in for ingress-nginx v1.12.0
7	Azure	1.30	4.11.3 *	stable:2024.12	annotations-risk-level: Critical	Expected cm value set for stable:2024.12 cadence and stand-in for ingress-nginx v1.12.0
8	Azure	1.30	4.11.3 *	stable:2024.11	strict-validate-path-type: 'false';annotations-risk-level: Critical	Expected 2 cm values set for lts:2020.03 cadence and stand-in for ingress-nginx v1.12.0

• For the development tests 6-8, chart version v4.11.3 was used as a stand in for the upcoming v4.12.0 to verify config map values are being set based on the latest ingress-nginx version, ingress-nginx version comparison value was adjusted in the dev branch after completing those tests.

[saschjmil]

LGTM