cleanup acquisition base categories in categories and properties definition
We no longer use order/delivery category to acquire categories and properties. Having needless acquisition base categories in category/property definition makes accessor slower. Yes, category accessor is slow in ERP5. So I propose to drop order and delivery from acquisition base categories from generic business templates.
One thing I'm still wondering is specialisethat is only used in variation's acquitision base categories. Is it really required ? I think that in getAggeregatedAmountList() usage, specialise is anyway taken into account by asComponent() result and we don't need explicit acquisition in variation base category. At least I find no reason to have specialise only in variation.
/cc @nexedi