Update submodules.
Update simpletest to new version with some small fixes.
Update notorm
Update simpletest again.
Update HSBC, basic index page.

Updated HSBC Bank Class.
 - Now works with secure login
   - Saves cookies between runs to attempt to not require the securekey to
     be entered too often. (At least during development anyway.)
 - Fix for parsing multiple transactions per day not adding +1 second in
   all instances.
 - Handle accounts with no sort code.
 - Updated html "cleaning" etc.
 - When obtaining historical transactions, go both forward and backwards
   to work around buggy HSBC display of historical statements

Account and Transaction objects now have a fromArray() function

Account now provides the ability to sort transactions rather than returning
them in the order they were discovered.

Basic index page that shows all known transactions/accounts. Used
currently to test that the import actually returns a sane set of
transactions (ie, they all correctly follow on from each other)

Update SimpleTest, again.
Add Halifax Support
"changetype" in Transaction is now a human-readable description.
"typecode" is the old "changetype" (this is used in the hash)
htmltidy is now run in utf8 mode
getAccounts() and updateTransactions() now bail if their first page
request does not result in a logged-in page.
Update simpletest.
Start on TescoBank Support.

This has the ability to log in. Yay.
At the moment, this does require the php v8js module, as we need to run some Javascript to generate OTPs as part of this login process.
At some point I may look at converting the OTP code from JS to PHP, but for now this seems easier as the JS comes from the HSBC login process and is what a browser would do.

The usual getAccounts() and updateTransactions() functionality to follow.
Update simpletest.
Update simpletest.
Remove Debugging, improve TescoBank

newBrowser() now uses isLoggedIn() rather than the old HSBC check.
Correct some documentation in Halifax
Remove some old debugging
TescoBank now actually pulls out credit card data! (Only for the last few months though as that is all that is sanely available. Will look into PDF parsing to expand this to 18 months.)
Don't skip most recent day transactions.

There doesn't appear to be any need for this, as any new transactions will appear above what we currently have, and will thus get the correct dayCount added to their time still.