Fix data tag related tests

[Ruchip16]

SUMMARY

This PR addresses and resolves several failing unit and integration tests in the ansible.utils collection caused by recent changes in Ansible 2.19’s templating system.

also related to #398

Root Cause:

Starting with Ansible 2.19, the internal behavior of the Jinja2-based templating engine has changed. Specifically:

• Undefined values (e.g., AnsibleUndefined) are now intercepted earlier by the Templar.
• These values no longer reach filter functions directly. Instead, the Templar raises a TemplateError or TemplatePluginError before any filter logic is invoked.
• As a result, unit tests that manually create and pass AnsibleUndefined values to filters (bypassing the Templar) are invalid and misleading, since such situations will not occur in actual playbook execution.

Additionally, some integration tests showed inconsistent behavior across Ansible versions (e.g., 2.17, 2.18 vs 2.19) due to how JSON was read and interpreted from file lookups:

• In certain environments, lookup('file') returned a raw string, which caused the validate filter to behave incorrectly.
• This inconsistency has been resolved by explicitly parsing input data and criteria using the from_json filter

Fixes the certain failing unit and integration tests in utils

IMPACT

In Ansible 2.19, undefined values (like AnsibleUndefined) no longer reach filter functions directly. Instead:

• The Templar catches them earlier and raises a TemplateError or TemplatePluginError before the filter even runs.
• So tests that manually create and pass AnsibleUndefined to filters are invalid now.
• The ipaddr filter does not support undefined values, so there’s no point in testing that behavior anymore.
• Ensures test consistency across Ansible versions
• Avoids false positives or misleading failures in CI due to template handling differences.
• Aligns tests with the intended and supported behavior of Ansible 2.19+.
• Removes reliance on Ansible internals (Templar, _internal._ambient_context, etc.) for unit tests that do not require them.

ISSUE TYPE

• Bugfix Pull Request

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/05563eaa5db74c1f922b8abec4da85a8

✔️ ansible-galaxy-importer SUCCESS in 3m 13s
✔️ build-ansible-collection SUCCESS in 5m 45s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/a3e61765e55d49a7be1db419ad84d2c1

✔️ ansible-galaxy-importer SUCCESS in 3m 11s
✔️ build-ansible-collection SUCCESS in 5m 48s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/d1542be11f6b46f192a4dda5640303dd

✔️ ansible-galaxy-importer SUCCESS in 7m 49s
✔️ build-ansible-collection SUCCESS in 5m 54s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/9c54980dd8ff470cb438cbc14e6572bd

✔️ ansible-galaxy-importer SUCCESS in 3m 19s
✔️ build-ansible-collection SUCCESS in 5m 42s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/d7bc2bad265646a6810d7948d5eae8fe

✔️ ansible-galaxy-importer SUCCESS in 3m 24s
✔️ build-ansible-collection SUCCESS in 5m 44s

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/28a766d2e0ae47d4bd4facb9c48f1813

✔️ ansible-galaxy-importer SUCCESS in 3m 53s
✔️ build-ansible-collection SUCCESS in 5m 56s