Add config argument to more password.Password invocations. The work done to allow password_pbkdf2_default_rounds to be overridden for testing requires that calls to password.Password include a config argument. This was needed because using the real value more than quadrupled testing runtime. However there are still a few places where config was not being set when Password was called. I think this fixes all of the ones that are called from a function that have access to a db.config object. The remaining ones all call Password(encrypted=x). This results in Password.unpack() being called. If x is not a propertly formatted password string ("{scheme}...", it calls encodePassword. It then should end up raising the ConfigNotSet exception. This is probably what we want as it means the shape of "x" is not correct. I don't understand why Password.unpack() attempts to encrypt the value of encrypted if it doesn't match the right form. According to codecov, this encryption branch is being used, so somewhere x is of the wrong form. Hmmm....

<tal:block metal:use-macro="templates/page/macros/icing">
<title metal:fill-slot="head_title"
 i18n:translate="">Registration in progress - <span i18n:name="tracker"
 tal:replace="config/TRACKER_NAME" /></title>
<span metal:fill-slot="body_title" tal:omit-tag="python:1"
 i18n:translate="">Registration in progress...</span>
<td class="content" metal:fill-slot="content">

<p i18n:translate="">You will shortly receive an email
to confirm your registration. To complete the registration process,
visit the link indicated in the email.
</p>

</td>
</tal:block>