feat: pass config to NamedTuple fields

[rorybyrne]

Change Summary

This PR changes the way pydantic validates NamedTuple fields. Currently, a new vanilla BaseModel is created dynamically for the field, and used for validation. This PR simply passes the parent model's Config to that newly created model, allowing settings like allow_arbitrary_types to be propagated to the attributes of NamedTuple fields.

Related issue number

fix #4219

Checklist

• Unit tests for the changes exist
• Tests pass on CI and coverage remains at 100%
• Documentation reflects the changes where applicable
• changes/<pull request or issue id>-<github username>.md file added describing change
  (see changes/README.md for details)
• My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

[rorybyrne]

please review

[PrettyWood]

Thanks good catch! Passing the config to TypedDict has been added recently. We should have done it for NamedTuple at the same time

[rorybyrne]

Sweet, thanks for the quick review ❤️

[hramezani]

@synek Thanks for your patch 👍

[hramezani]

Please update

[rorybyrne]

Thanks for the review @hramezani. Do you need any other changes, or is the PR ready?

[hramezani]

Thanks for the review @hramezani. Do you need any other changes, or is the PR ready?

No, we actually waiting for @samuelcolvin for final review

[samuelcolvin]

thanks so much.