credential: create assignmnent starting the day before today.

Funny things can happen if you have multiple machines and their clock are not
synchronized.
crm: rename action
CRM: remove unused form
CRM: Introduce a script to easily customize the portal type of response events to be selected by default in reply dialogs
CRM: Introduce a script to choose the content type of response events
whitespace cleanup
move captcha style to a css class so that it is easily customisable
CatalogTool: fix searchAndActivate when called with a condition on 'uid'

Because the method internally overrode 'uid' after the first group of objects,
passing a list of uids could make it go berserk and activate all objects in
catalog with an uid greater than those of the first group.

Although searchAndActivate was not initially written to be called with such
list, this commit fixes this instead of forbidding conditions on 'uid',
since it remains useful to easily split & group activities.
fix wrong usages of declarePublic().
fix a typo in declarePrivate() argument.
we no longer need to setup bin/ and etc/ directories for unit tests.
we don't use ClockServer. we use TimerService instead.
fix a typo.
delete unused code.
invoke getPriceCalculationOperandDict script in unrestricted_apply.

so that :
* the result is stable.
* no permission is required for Supply and Resource only for price calculation.
* no proxy role is required in script.
fix way to get stopdate from gadget form
fix conditions to display knowledpad tools.

(cherry picked from commit 23da3f0da015e77592c7cf1bccb3320fd08351c7)
erp5_knowledge_pad: drop complicated and broken logic to wait that new pads are indexed

This fixes many different bugs, like random Unauthorized errors when a
knowledge pad is deleted.

When an object is created, calling immediateReindexObject is only a performance
coding crime, which should be negligible since pads are objects that are not
created often. Previous implementation was certainly even less scalable due to
the many extra requests done to wait that new pads are indexed.

If immediateReindexObject is too slow, a distributed cache could be used
instead. This is not trivial and overkill for the moment.

It would be better if we didn't have to rely on the catalog. IOW, data could
have been organized differently so that in ZODB, pads are grouped in containers,
1 per user.
Merge "erp5_knowledge_pad: drop complicated and broken logic to wait that new pads are indexed
Template Tool: Ignore totally the update of Business Templates that are inside keep_bt5_id_set