WIP on projects testing for user; one test failing

The third test is failing with stale element reference errors. I don't
know why yet, but it's time to check in what I've done so far. The fix
should be simple once I figure it out, but stale element references do
tend to be a bit mysterious.
WIP on setupTestEnvironment.php: mostly works

The setupTestEnvironment.php script is now mostly working. It still has
one flaw: it cleans out the sourceforge_test database but doesn't touch
the project databases for the test project(s). This results in extra
texts being added to the test project when the setup script is run
several times, which could lead the E2E test scripts to fail if they end
up clicking on the wrong text. A later version of the setup script
should clean up the database for the test project(s) as well as the
scriptureforge_test database.
WIP on setupTestEnvironment.php: working now

Now the setup script also cleans out the databases for the two test
projects, so that they are guaranteed to start afresh. This should be
ready to start adapting our E2E tests to use it.
Stop using setupTestEnvironment.js

Now using setupTestEnvironment.php instead, in the various rune2e.sh
scripts. The Javascript setup script is no longer required, which
removes about 60 seconds from the runtime of each run through the test
suite.
Switch change-password test to use new login page