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.

Even if object is still reindexing, reference concurrency shall be protected,
and no double objects are created.

As users can double click (or register in same time with same reference)
during time of indexation, it is required to lock on activity system.

Note that as reference is global in the system, same tag, as in
Document.Person._setReference is used.

ERP5Site_newCredentialRequest shall disallow to create duplicated credentials.

CredentialRequest_checkLoginAvailability was used only on form, but script
shall not trust that form correctly validated everything, so recheck here too.

And another test to show behaviour of run-once interactions on temp objects
affecting real-objects.

And a global search/replace on assertEquals -> assertEqual on
testInteractionWorkflow.py

Only prevent transition from running if it has actually run. If its guard
prevents it from running, consider it still runnable in this transaction.

This change doesn't help to skip the interaction on the real object if it's
not forbidden on the temp one.

Mark as NotImplementedError, as use case is not described yet.

portal_instrospections is been used by SlapOS as a single place for detect
lack of configuration (ie.: Missing bt5s, Missing memcache configuration...)

Move to tnstance creation make things cleaner and it creates a standard
place for information collection.

login.

Otherwise it can't be set, just like variation_category_list

and account's number of failures and stop user (if required) from
logging in.

this should have been part of commit 79a2aaf5