This method was refactored to:
 - automatically resolve and install business templates dependencies if requested.
 - Make possible use activities and prevent long transactions.

This method comes from previous Implementation.

Due the presence of object_to_update, the API will never update the catalog
if we do not provide explicitly values.

The API resolveBusinessTemplateListDependency is able to return a list
of BT5 with URL and include all dependencies.

This introduces flexibility, and permit this method be reused in
different ways.

Business Template API itself should detect if update catalog is mandatory
or not, instead force never update.

installBusinessTemplatesFromRepositories uses plural, which is a code crime,
Keep it deprecated to preserve backward compatibility.

If Business Template is not present, returns None.

There was several tests specifics to TemplateTool into testBusinessTemplates
This commit move tests to appropriate test suite.

No Contract field shall be rendered, and no need to confirm.

Cover cases of ERP5 portal and Web Site contexts. Use anonymous and check
that returned page contains correct links and that those links are rendered
correctly.

Support classical style and web site style.

Provide new preference, which if set can be used to find portal global
contract document.

954e399c introduced typos.

Provide sensible defaults.

When form is rendered while being not logged in, what is default way of using
this form, ERP5Site_getAuthenticatedMemberPersonValue returns None, so add
condition which does not log failures.

Add required submit. Fix expected string.

It is required in order to have loggable person after credential request.

No credential request is automatic, only approval, so submit credential request.

Setup assignment, in order to have loggable user.

As beforeTearDown stabilised credential preferences, test are running with
default setup, so it is required explicitly set preferences.

Thanks to this another configuration will not leak between tests.

Without assignment setup during creation, no user would be created.

Cleanup is done in beforeTearDown, no need to add it in test.

Because of wrong reset to defaults, a lot of tests were assuming wrong message.

There is no need to repeat step in each test, as beforeTearDown hook
can be used in such case.

According to method name it sets all credential preferences to default state,
but some are overriden.

It directed to uncontrollable test results.