Refactored Timestampable model behavior.

[SidRoberts]

Hello!

• Type: code quality
• Link to issue:

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 updated the CHANGELOG

Quick question: Why would anyone want to update multiple fields with the same timestamp? Could we remove this functionality?

[codecov]

Codecov Report

Merging #14027 into 4.0.x will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            4.0.x   #14027      +/-   ##
==========================================
+ Coverage   68.62%   68.62%   +<.01%     
==========================================
  Files         470      470              
  Lines       95148    95158      +10     
==========================================
+ Hits        65294    65301       +7     
- Misses      29854    29857       +3

Impacted Files	Coverage Δ
ext/phalcon/mvc/model/behavior/timestampable.zep.c	65.75% <0%> (+0.67%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1d4e2f1...eb63c84. Read the comment docs.

[sergeyklay]

@SidRoberts Is it ready to merge

[sergeyklay]

N.B. Could you create a new issue for "Quick question" to allow other contributors a chance to speak up, and to take a fresh look at this issue later.

[SidRoberts]

@sergeyklay It is ready.

[sergeyklay]

@SidRoberts Could you please rebase

[niden]

Thank you @SidRoberts