Stop traversing zend_execute_data when certain conditions are met

[sj-i]

On another optimization idea.

In tracing applications using frameworks such as Laravel, there are calls inside the framework in closer to the root of the call hierarchy, and you may not be interested in the performance inside the framework.

Since traversing zend_execute_data goes from the end of the call hierarchy towards the root, it is possible to stop traversing once the entry point from the framework to the application is detected by specifying a regular expression or something similar.

This method is incompatible with #158, but it is worth a try since the total amount of memory copy can be reduced in this way.