Adding more examples.

This adds example usages of:
* using the WalletAppKit
* restoring a wallet from a seed
* sending coins
* implementing a WalletEventListener
Cache deterministic seed
Minor whitespace changes.
WalletTemplate: Small visual tweaks
Add shade plugin to wallettemplate
HD Wallets: final part needed before release.

If a key is seen in a filtered block that is too far inside our lookahead zone, discard that block and any further blocks being sent to us by a remote peer and recalculate the Bloom filter after more keys are pre-calculated. Then restart the chain download process. This ensures that we can catch up/replay the block chain and keep up with the deterministic key sequence.
Parse verifyFlags from script and tx JSON tests. In addition to P2SH (previously known as enforceP2SH), NULLDUMMY is implemented.

Update all script and tx JSON tests from Bitcoin Core.
Removing the check for against the number of coins available. It is possible that when displaying a caclulated number of coins (for example number of coins transfered over a period of time), will exceed the actual number of coins available. Additionally, this doesn't check the number of coins that have already been created, so the check is very limited. It's better to perform more contextual checks during the initiation of a transaction and other places where it is applicable.
Removing MAX_COIN and MAX_MONEY checks from Coin, as each network can specify its own values and it is possible that values larger than MAX_COIN/MAX_MONEY could be used (for example, when tallying up the total amount in transactions, to show the volume of money changing hands). Also, these checks do not have any relevance to the amount of money that is actually available. Checks for MAX_MONEY or MAX_COINS should and do happen where they are contextual to a particular function like sending a transaction.
Changing MAX_COIN and MAX_MONEY to instances so each network can specify its own values.