Collection documentation: do not wrongly interpret plugins/modules whose name starts with _ as deprecated

[felixfontein]

I'm not sure whether an issue exists for this I can reference. I spotted this while working on #3607 and noticing that a plugin in a collection I was uploading for testing was wrongly marked as deprecated.

In ansible-core itself, an underscore was interpreted this way also in ansible-doc and the validate-modules sanity test (but nowhere else), but that was changed for 2.15.

Ref: ansible/ansible#79362

[felixfontein]

Not sure whether the changelog fragment's filename is OK like this; I took the PR's # since I'm not aware of a AH Jira issue.

[himdel]

Good catch 👍

AAH 4.6 / AAP 2.3 is core 2.14, so we'll only want this in 4.7+, right?

[felixfontein]

AAH 4.6 / AAP 2.3 is core 2.14, so we'll only want this in 4.7+, right?

They weren't really deprecated in ansible-core 2.14 either, it was just that valide-modules somehow assumed so and that ansible-doc showed them as deprecated and at the same time printed their name wrong (it removed the underscore).

Not backporting to 4.6 is probably saving some discussions so ... it's probably better :)

[patchback]

Backport to stable-4.7: 💚 backport PR created

✅ Backport PR branch: patchback/backports/stable-4.7/e0387b92a4581383abb8390e086d103bd3251af9/pr-3715

Backported as #3732

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

[felixfontein]

@himdel thanks for reviewing and merging!

[himdel]

Any time :)