4.2.3 General Behaviors Update...

[belisoful]

This fixes #891, #851, and #838

• TClassBehavior tracks owners with TWeakList
• Attaching IBehavior to Class clones instances for each owner/instance. the standard action was to instance from a class name string or array of class/properties.
• TComponent::__destruct clears the behaviors and event handlers for better garbage collection.
• IBaseBehavior has Enabled flag. Thus, IClassBehavior has enabled flag. Simplifies TComponent behavior processing.
• TBaseBehavior records its unique attachment name in the owner. IClassBehavior can only install on one name across all owners.
• Attaching a behavior over an existing name properly removes the prior behavior.
• TBehavior and TClassBehavior track the behavior enabled status of their owner by dynamic event dyEnableBehaviors and dyDisableBehaviors for turning on and off their attached event handlers. This is eating your own dog food.
• Changing the enabled status of a component synchronizes its behaviors event handler attachments.
• Disabling an owner behaviors or disabling a single behavior will detach its registered handlers from all.
• Flag for whether to detach handlers when disabled
• EventsLog to hold a cache of the behavior events, for Closure retainment. Now supports Closures as behavior event handlers properly.
• TBehavior tracks its owner with WeakReference. For better garbage collection.
  • Both track the attachment status of the event handlers in their owner and owners.
• IClassBehavior file creation author properly attributed. Class Behaviors were never a thing in that time in PRADO.
• Behaviors can implement TComponent dynamic events on owners without being self called when calling their own TComponent methods (that call the dynamic event). Behaviors work better with its own dynamic events. -TComponent::disableBehaviors makes special implementation for dyDisableBehaviors after Behaviors are Disabled so behaviors can act accordingly because behaviors are disabled when the behaviors' dynamic events are raised. -TBaseBehavior implements getStrictEvents to say whether the events are mandatory to attach or optional.
• Error Messages
• Updated documentation on behaviors in TComponent and in Behaviors.

[belisoful]

my PHP Stan got removed while swapping, the errors were because my phpStan wasn't working right. reinstalled. found errors.

I have spent an enormous amount of Time proofing and vetting this and the php documentation.

Unless you find something: this is ready for merge.