Updated submodule to point to origin/stop.
Updates required after removing Dispersy Singletons and Member cache.

All Singleton methods are no longer available:
- dispersy.has_instance
- dispersy.get_instance
- dispersy.del_instance

The Dispersy instance is available directly from the LaunchManyCore,
or though the session instance (session.lm.dispersy).

Also, DummyMember and Member instances should only be created through
Dispersy using:
- dispersy.get_temorary_member_from_id (returns a DummyMember)
- dispersy.get_new_member
- dispersy.get_member
- dispersy.get_members_from_id
- dispersy.get_member_from_database_id
Modified Dispersy.has_instance() to use the dispersy instance from the ChannelCommunity construtor.
Undo change that should be local only.
Updated to new code.

- dispersy_database -> dispersy.database
- join_community(master, ...) -> join_community(dispersy, master, ...)
- DummyMember(cid) -> dispersy.get_temporary_member_from_id(cid)
Point back to the normal tribler repository.

The origional change should not have been committed in the first place.
Removed more Dispersy.get_instance() calls.
Dispersy is responsible for starting and stopping.
Point to the dispersy repository containing the 'stop' changes.
Load communities durint define_auto_load.

It is not possible to load communities during Dispersy.start because
the community parameters depend on having a Member, and creating a
Member depends on Dispery.start having finished.  Hence Dispersy.start
no longer loads all communities, instead, this can now be done by
define_auto_load.
Must point to boudewijn-tribler repository for dispersy stop changes.
Removed obsolete code.
Add debug information.
Add debug information.
Dispersy.start must be called before the cachedb starts.
Load communities after cachedb.
Merge remote-tracking branch 'remotes/upstream/devel' into origin-dispersystop

Conflicts:
	Tribler/dispersy
Close database transaction when _callback stops.
Do not raise exception during shutdown.
Remove duplicate code.