Former version looked for a matching predicate on caching policy and a Enable304
property set to true. No we stop on first predicate, thus disabling 304 answer
when enable 304 is not selected

Caching the current user during the transaction breaks code that changes user.
getSecurityManager().getUser().getId() is anyway already so fast, and it is
here called so rarely, that it's not worth caching the result.

The presence of the password in the Credential Update should not change the processing workflow
of the Credential Update. For Now we just update the password and leave to rest to normal process

If the email is not already set during acceptation

erp5_free_subscription: Do not add Free Subscription Request to a user but can be added to a person with the same email

For Base_viewKnowledgePadMacroLibrary

Conflicts:
	product/ERP5Security/__init__.py