Migrate remaining schemas to pydantic 2

[felixfontein]

Currently contains #331. Will rebase once that has been merged.

• Rebase to remove Avoid using pydantic compat layer where easily possible #331 once merged.
• Remove TEMP commit once Pydantic: add helper, generalize forbid extra code antsibull-core#169 has been merged.
• Release new antsibull-core version with Pydantic: add helper, generalize forbid extra code antsibull-core#169.
• Bump antsibull-core dependency and remove TEMP commit once antsibull-core 3.2.0 is out.
• Migrate docs schemas to pydantic 2.

[felixfontein]

@gotmax23 I managed to convert all pydantic v1 models to pydantic v2. That also means that ansible-community/antsibull-core#169 is sufficient as-is and does not need more changes for the documentation schemas.

[felixfontein]

Hmm, the reasoning doesn't work due to how options etc. work - the keys there are arbitrary strings that users provide. There exist modules whose option names are starting with upper-case letters :(

For example, amazon.aws.elb_application_lb has a (nested) option listeners.DefaultActions[].TargetGroupName.

[felixfontein]

Fixed in adcc19f.

[gotmax23]

Looks like everything except coverage (with a less than 1% difference...) is passing. I'll do one last look through, and also try to run a test package docs build in ansible-documentation's CI.

[gotmax23]

try to run a test package docs build in ansible-documentation's CI

ansible/ansible-documentation#1923

[gotmax23]

You've addressed my feedback, and I looked at this pretty closely the first time, so ACK, pending the new antsibull-core release and version pin updates.

[felixfontein]

@gotmax23 thanks for reviewing this!