fixup! fixup! authentication_policy: check isPasswordValid on the login corresponding to that username

Useful in the context of password reset

Base_getUserValueByUserId and Base_getUserIdByUserName

When current password was incorrect we still have to redirect

Conflicts:
	product/ERP5/bootstrap/erp5_core/SkinTemplateItem/portal_skins/erp5_core/PreferenceTool_setNewPassword.xml

introduced by hand edit of XML

When authentication policy is in used, this method allows for checking
that the provided password can be used for the login referenced by this
password_key

This is a change in the API, previously only "messages id" were
returned.To make it easier to reuse analyzePassword in other contexts,
we now return the message directly.

isPasswordValid returns a boolean value, so we should check it's true
rather than <= 0

method signature should not contain self

Fixes [#20161227-D1FA4](https://nexedi.erp5.net/bug_module/20161227-D1FA4)

Also modernize code by using set() and not using
ERP5Site_getAuthenticatedMemberPersonValue

it should be displayed if user can add a credential update

fix NameError introduced in a97402d3

Tests should not depend on the state left by the previous test run.

This was achieved by:

* use a different preference in each method to reset the state of preferences configuration.
* clear cache after setting preferences, so that the new preference setting is used
* change password after setting the max preferred password lifetime duration, otherwise password event are not created and password is not detected as expired.
* rename test methods not to include number, we should not force test ordering, since we want tests to be independant.
* Also add one case of password actually expired

Before this change, password event were only recorded when
preferred_number_of_last_password_to_check was set.

We also need to record password events to check for password lifetime,
so also record password events when preferred_max_lifetime_duration is
is set (also when set to 0h, but this only makes sense in tests).

testAuthenticationPolicy was not showing this problem, because tests were not properly
isolated and test_02_PasswordHistory was enabling
preferred_number_of_last_password_to_check for all other tests.

https://www.erp5.com/bt5-Module.Creation.Guidelines

> Rule: In view mode, simulation_state or validation_state fields should be in the bottom of “right” group

according to https://www.erp5.com/bt5-Module.Creation.Guidelines *3.3 Listbox rules*

> If a listbox is configured so that only objects from one portal type can be displayed, then the title of the listbox should be set to the plural of the given portal type title (ex : Sale Orders should be the title of a listbox displaying "Sale Order" objects).

This was broken since the use of user_id on Person.
Also, add a test.