fix: respect ancestor property tags in model extensions

[spawnia]

• Added or updated tests
• Documented user facing changes
• Updated CHANGELOG.md

Changes

Ensure the model extensions considers PHPDoc @property tags from ancestors, not just the model class itself.

Breaking changes

None.

[szepeviktor]

Hello Benedikt!
Thank you for your work.
Are you sure you want to encourage users to manually add many-many properties?
Larastan has a lot of effort recognizing magic properties in Laravel.

[spawnia]

I think it is great that Larastan can recognize magic properties, but there are still situations that require an escape hatch:

• BelongsTo or HasOne relations that are guaranteed to be non-null (backed by a non-nullable foreign key constraint)
• specializations of generic implementations in a parent class, e.g. parent defines getIdAttribute(): int | string, but the ID is known to always be string in a given subclass

Larastan seems to recognize the necessity of this, given there is already an early return if a property annotation exists. I don't see why this logic should not extend to annotations from ancestors.

[canvural]

Thanks! I had the same thing in mind actually.

Just left one remark. And after that I will refactor the test cases for this.

[szepeviktor]

• BelongsTo or HasOne relations that are guaranteed to be non-null (backed by a non-nullable foreign key constraint)

• specializations of generic implementations in a parent class, e.g. parent defines getIdAttribute(): int | string, but the ID is known to always be string in a given subclass

I would still welcome these features in Larastan.

[canvural]

Thank you!