Update GenericAttributeImpl to work with SqlAlchemy 2.0.22

[danigm]

This change fixes the issue, but I'm not sure if this should be fixed in SQLAlchemy directly.

I've been debugging and found the problem in this call where there's a missing parameter. Looks like the AttributeImpl class now requires 4 positional parameters, and the register_attribute mapping is not calling this correctly.

Fix #719

[josecsotomorales]

Reported this issue kvesteri/sqlalchemy-continuum#339 and ended up here, what's needed to merge this PR?

[josecsotomorales]

@kurtmckee can you take a look at this?

[stabacco]

I'm also interested in this to be merged. Currently I have to pin the sqlalchemy version to 2.0.21

[kurtmckee]

Test suite appears to be failing for unrelated reasons.

@danigm Thanks for contributing this fix!

[josecsotomorales]

@kurtmckee @kvesteri happy to be a contributor to this project to get this released

[marksteward]

Does this fix retain compatibility with 2.0.21?

[marksteward]

I've tested this and I don't think it does the right thing for sqla < 2.0.22, including 1.4.

register_attribute_impl is actually called a few lines above, which has a different signature. Previously they all took 4 positional arguments.

So to avoid breaking anyone who doesn't immediately update to 2.0.22, I think this code needs to count the number of args, and only add the extra typecallable if needed. Though it's not clear to me that it was ever appropriate to pass typecallable in as callable_. Frankly this whole thing needs rewriting.

[josecsotomorales]

@marksteward I haven't looked at this yet, this was merged to master tough, I will try to get tests to at least pass with the current master version in this PR first, then come back to this, if you can help with a PR