WIP 2.19 Porting Guide stub with data tagging

[nitzmahone]

We're linking to this PR as temporary documentation for the pending Data Tagging changes to core.

This PR won't include any other 2.19-specific Porting Guide entries.

[ansible-documentation-bot]

Thanks for your Ansible docs contribution! We talk about Ansible documentation on Matrix at #docs:ansible.im if you ever want to join us and chat about the docs! We meet on Matrix every Tuesday. See the Ansible calendar for meeting details. We welcome additions to our weekly agenda items too. You can add the dawgs-meeting tag to a forum topic to bring it up at the next meeting.

[ansible-documentation-bot]

Thanks for your contribution, @nitzmahone! Please make sure that your pull request includes sufficient and meaningful details in the description.
PR descriptions provide important context and allow other developers and our future selves to understand a change's rationale and what it actually fixes or accomplishes.

[ssbarnea]

@nitzmahone I managed to get very close with linter changes (only 10 test failures) but I spotted an unexpected exception when I call:

ModuleArgsParser(sanitized_task).parse( skip_action_validation=True) 

With 2.18 code, my call succeeds but with this PR it raises:

"Complex args containing variables cannot use bare variables (without Jinja2 delimiters), and must use the full variable style ('{{var_name}}')"

My task looks like:

{'name': 'Ansible-lint for args rule should succeed (Bug - 3199)', 'vars': {'copy_vars': {'src': 'args.json'}}, 'action': 'ansible.builtin.copy', 'args': '{{ copy_vars }}'}

I am not sure how to make it pass with 2.19.

[gotmax23]

Thanks for working on this. What's the current status with this PR? The Steering Committee would like to notify collection maintainers about this change, but it'd be nice to link to official docs instead of a draft PR.

[gotmax23]

The text is clear and informative. I left some style nits.

[gotmax23]

In https://docs.ansible.com/ansible/latest/dev_guide/style_guide/preferred_terms.html#preferred-terminology, I think either Ansible Core or ansible-core is preferred, but @samccann can probably clarify.

[gotmax23]

Should trust_value() have an example or further documentation, or are you waiting until the public API is more complete/stable?

[nitzmahone]

We're still working out where the actual docs for those things will live- none of the current options are great 😐

[nitzmahone]

@samccann Since core 2.19.0b1 is already out there, we should probably get this one merged and published pretty soon- still an open question on the quoting of ansible-core, and of course any other feedback you've got is welcome- thanks!