Use AccountHistoryChunk#mixIn for printSubView

[michielbdejong]

The current code would match floater transactions even if they're years apart. Let's set a max date skew of say 7 calendar days, and not match if the difference is bigger than that.

Also, the floater-matching code should move from run.js to a newly created class MultiChunkAccountHistory.

• check if a mutationToSelf is in-chunk for both the sender and the receiver account. So maybe the sender composes chunks of implied bank-to-bank transactions, and sends those to the receiver, who then tries to match them up with AccountHistoryChunk#mixIn or something close to that.

[michielbdejong]

Don't try to match if only one of the two accounts is in-chunk for the date of that mutation.

[michielbdejong]

Primary channels can be:

• "me - bank account" (bank statement)
• "me - group" (WieBetaaltWat)
• "shop - me" (Invoice)
• "bank account - shop" (Bill Payment History)

Secondary channels can be:

• "my one bank account - my other bank account" (de-dupe!)
• "bank account - shop"
• "group member - shop" (de-dupe!)

Tertiary channels can be:

• "shop - me"
• "shop - other group member"

if you link a WieBetaaltWat entry to a bank statement entry, make sure to de-dupe it. Also you may have seen the payment in a shop's billing history.

Direct netting:

• Alice gives goods to Bob and her (group or bilateral) debt to Bob decreases. Nobody else is involved.
• You receive interest or are charged for the cost of using a bank card.

Indirect:
Alice -> Bank -> Shop
Alice -> Bank -> Bank -> Shop
Alice -> Bank -> Bank -> Bank -> Shop
etc.