Move configurator after script from Business Template to Workflow. This will make management easier

Instead get Informations from the Business Configuration, get information directly from the Workflow Document. This easly creates a identity if the workflow and also simplify the process of Pré-configuration.

This file is a generic element.

Now title and Descrptions is used to present messages to the user.

Instaead use spreadsheet use directly workflow informations to present information at the screen during the configurations. This turn Workflow creation much easier.

Conflicts:

	bt5/erp5_configurator_standard/bt/revision

Conflicts:

	bt5/erp5_configurator_standard/bt/revision

This property is going to be used to define if the installation of the business template will install
all dependencies or not.

Those files should be merged in future.

 - Check if the bt5 is already installed, this is not a change of behaviour, just a performance improvement
 - Cache getInstalledBusinessTemplateTitleList, because it doesn't change during the build and it is a bit time consuming do it so often.
 - Use activate and install_dependency, this can make bt5 list shorter and make core relies on BT5 definitions.
 - Build should wait for updateBusinessTemplateFromUrl
 - Automatic Dependence handling updateBusinessTemplateFromUrl is invoked using activities.

Dropped last_id on XML

provide a good default value for migrateToHBTree()'s new_generate_id_method argument, suggested by Tatuya.

Also, declare ERP5Site.getVersionPriorityNameList() as protected rather than
private for views.

This is similar to portal skins priority, except that versions and priorities
are defined on ERP5Site (as 'VERSION | PRIORITY' where PRIORITY is a float) as
there is not one Folder for each version in contrary to portal skins.

On the Business Template itself, versions and priorities can be defined like
'VERSION | PRIORITY' or simply 'VERSION' (where PRIORITY is assumed to be
0.0). Upon installation, it will be merged into ERP5Site property in
descending order (by priority first and then by version for versions with the
same priority).

considered as a Document for DMS for example.

When load() was called in checkConsistency where namespace_dict was not given
and thus equal to the default function parameter value, exec would set the
function namespace_dict parameter, thus the next call would have
namespace_dict already set when it was given.

This fixes testInvalidSourceCode when being ran for TestZodbExtensionComponent
and TestZodbDocumentComponent in the same runUnitTest.