Make ready for data tagging

[felixfontein]

SUMMARY

This adds ansible/ansible#84621 to CI to test whether it causes problems in CI.

Ref: https://forum.ansible.com/t/data-tagging-preview-and-testing/40759
Ref: https://forum.ansible.com/t/data-tagging-playground/39909

ISSUE TYPE

• Test Pull Request

COMPONENT NAME

CI

[ansibullbot]

cc @gundalow
click here for bot help

[ansibullbot]

cc @alpex8 @m-a-r-k-e @rlenferink
click here for bot help

[felixfontein]

@russoz regarding the YAML plugin, what do you think about the following:

1. move the removal of the yaml callback to community.general 12.0.0 (right now it's announced to be removed from 13.0.0);
2. wrap the definition of MyDumper in a try/catch that - inside the catch block - does some imports of internal ansible-core things to "make it work".

That way we only have to support it up to ansible-core 2.20 (which hopefully will limit the number of breakages caused by the internal imports to a minimum).

We could even remove it from 11.0.0 (the next release coming up in May) so we only ever have to support internals from ansible-core 2.19. But that would be not so nice for users since it only got deprecated in community.general 10.2.0 released on December 31st, 2024.

[felixfontein]

I removed 9becd3f since raw_get() has been added back temporarily, see ansible/ansible#84799 (comment).

[felixfontein]

wrap the definition of MyDumper in a try/catch that - inside the catch block - does some imports of internal ansible-core things to "make it work".

I have implemented this, and it works well.

@russoz what do you think of moving the removal of the yaml callback to 12.0.0 (instead of 13.0.0)?

[felixfontein]

(This is the first time that CI for this PR is actually green :) )

[felixfontein]

Restart CI.