Add the ability to get the transactions from the IB provider's accounts.

Criteria:

• Must be able to get the transactions for a given account from any browsed location
• An account must therefore have a UID within the provider, and be able to navigate to that account's transactions
• Must handle pagination of accounts
• Each row: datetime*, ref, description, amount* (+/-), new balance ; where * is mandatory.
• Ability to stop fetching once transactions are N days older than the latest cache
• Validate the cache where overlap occurs (balance $$$ may be variant without warning due to new transactions being added that predate existing cached transactions)

Pages that contains wacky and weird authentication, balances and transactions that can be relied upon for testing

Criteria:

• Transactions paginated through javascript
• Possibility for multiple authentication pages to get to the same balances/transactions
• Variety of CSS techniques, including randomly named elements, javascript obfuscated details etc.
• A guarantee that the pages will never be modified, only deleted (when no viable existing version is using it) or extended

A shiny homepage + some documentation on usage

Criteria:

• Hosted on pyggybank.github.io
• An awesome logo
• A clearly written purpose
• A prominent description on the terms of use

To save on accessing the IB resources too frequently, cache the results in an intermediate form.

Criteria:

• File based, plaintext (JSON / yaml)
• Doesn't need to be encrypted
• Needs to be configurable as to whether it happens at all
• Needs to be globally configurable as to how long a cache should remain in place (default an "1hr")
• Needs to be account-wise configurable as to how long a cache should remain in place
• CLI should be able to override cache length with --max-cache-age argument
• Cache age should be determined based on modification date