As it is possible to have non unique paths from Business Template point of view
(like having same file name for Test and Document) it is required to have "magically"
generated unique paths.

As Business Template internal data migration is unwanted, BusinessTemplate._objects
are not modified. So, while installing new Business Template, no magic is applied, but
becuase of different way of doing fresh installation and upgrade during fresh
installation problems of conflicting paths does not appear.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@45296 20353a03-c40f-0410-a6d1-a30d3c3de9de