Cycle: disable tokenizer

[roxblnfk]

ORM Schema compilation usually doesn't run in a production environment, but is loaded from the cache. This can affect the Memory Peak metric.
Perhaps it would be more correct to set the schema manually, rather than parsing files and attributes. #1 (comment)

Also removed unused packages.

I think the same is fair to do for Doctrine and Compositedb - to take out cache compilation. And in the startup script, use the ready result.
Then the Memory Peak metric will be collected under more equal conditions.

[compositephp]

Sorry, but now I'm uncertain about this PR for now. While I understand and respect your intentions to describe the model schema manually, my approach has been to maintain maximum consistency with real user scenarios. I think that majority of CycleORM users would opt for Annotated Entities rather than maintaining the manual schema in two separate places.

Additionally, I prefer not to delve into advanced fine-tuning and caching, as it can lead to unpredictable comparison conditions. I believe everything should adhere as closely as possible to the official basic documentation.

In the current benchmark, every ORM has almost identical model to scan and build it schema.

However, I'll take a closer look at Doctrine to see if it's possible to implement the same optimizations you made for Cycle without activating the caching layer. After this review, I'll be in a better position to consider applying your PR.