erp5_trade: move the composition cache in BusinessProcess.py

Since BusinessProcess.py was moved to portal_components, the cache in mixin/composition.py,
which was kept at the level of the zope process, was causing issue when portal_components
was reset : the classes kept in __class_cache would not get resetted, and later calls
to asComposedDocument would reuse them. In consequence, these classes would kept pointers
to objects in the old class BusinessProcess, causing bugs as these objects would have
been cleaned by the reset.

The first intuition was to remove this cache, unfortunately the reason of this introduction
(fixing a memory leak) is still valid nowadays, so I've decided to move this cache within
BusinessProcess, as it has the advantage of emptying it whenever portal_components is resetted.

For more information of the bug mentionned above, and the trials about removing the cache can
be found in the discussion of this MR :
!1032
4 jobs for fix-composition-cache in 0 seconds
Status Job ID Name Coverage
  External
passed ERP5.PerformanceTest-Master

running ERP5.UnitTest-Master

33486:35:11

passed SlapOS.Eggs.UnitTest-Master.Python2

00:22:56

passed SlapOS.Eggs.UnitTest-Master.Python3