Change Summary

This is a small change that brings BaseModel back into compliance with the the __set_name__ protocol defined in [PEP 487, and described in the creating the class object portion of the python documentation, which states:

the following additional customization steps are invoked after creating the class object:

• The type.__new__ method collects all of the attributes in the class namespace that define a __set_name__() method;
• Those __set_name__ methods are called with the class being defined and the assigned name of that particular attribute

In the case of BaseModel, some names in the original namespace (such as instances of ModelPrivateAttr) are stripped before calling type.__new__ with the new_namespace. As such, objects implementing this __set_name__ protocol are skipped.

Rather than calling type.__new__ with the original namespace, this PR implements the protocol directly by calling __set_name__ on any objects in the namespace that provide the method.

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

Context

For context, I've been using sqlmodel recently and would like to to implement this pattern

from sqlmodel import SQLModel

class SomeObject(SQLModel, table=True):
    name: str
    slug: str | None

    @on_before_save
    def _do_stuff(self):
        self.slug = slugify(self.name)

to bind object-specific listeners to various SqlAlchemy ORM events... however, this requires that the decorator know the class in which it is being called (which, among other things, seems to have been a primary motivator of __set_name__)