[#14810] Call model setters during ORM hydration in cloneResultMap()

[niden]

Hello!

• Type: bug fix
• Link to issue: [BUG]: Model setters do not call during hydration #14810

In raising this pull request, I confirm the following:

• I have read and understood the Contributing Guidelines
• I have checked that another pull request for this purpose does not exist
• I wrote some tests for this PR
• I have updated the relevant CHANGELOG
• I have created a PR for the documentation about this change

Small description of change:

Root Cause

cloneResultMap() — used internally by findFirst(), find() and all hydration paths — was directly assigning DB values to model properties, bypassing any user-defined setter methods (e.g. setName()). This was inconsistent with assign(), which respects setters.

Fix

Added the same setter-checking logic as assign() to all three property-assignment paths in cloneResultMap(), gated by the existing orm.disable_assign_setters setting (default false, meaning setters are called). Internal Phalcon setters listed in localMethods (e.g. setDirtyState, setSource) are excluded to avoid interference with the ORM's own lifecycle.

Files Changed

• phalcon/Mvc/Model.zep — setter-calling logic added to cloneResultMap() at all three assignment points
• tests/support/Models/InvoicesWithSetters.php — new test support model with setters that transform values
• tests/database/Mvc/Model/CloneResultMapTest.php — new testMvcModelCloneResultMapCallsSetters test (alphabetically ordered)
• CHANGELOG-5.0.md — added entry for [BUG]: Model setters do not call during hydration #14810

Thanks