Made Modifier\Observable's function names clearer

register -> registerObserver
unregister -> unregisterObserver
notify -> notifyObserver (this one's on the Observer interface)
Removes BasicLogicStore and ComparingStore

These classes were overengineered, and the flexibility they presented
realy wasn't necessary and was complicating things.

There's still going to be some simplifications possible due to their
removal, but I haven't done these yet.
Removes Store from Condition constructor

This was present to do a check that it wasn't checked against a store
other than the one it was created with. This check is also removed (as is
the requirement for it to be the same store). This was part of the same
overengineering as 901b79f3. Together with that commit, this should allow
some changes which make for a nicer API, as well as some new interesting
tricks with Conditions.
Removes createCondition functions from Store

And introduces the new API, in which the user can just create Conditions
him or herself. This is better because it allows users to create
Conditions without creating a Store first, it allows them to use a single
condition on more than one store (as long as it makes sense) and while the
names remain long, the use of namespaces gives control over how to write
it back to the user.

This was made possible by 035b4c0a and 901b79f3.
Moves process<some>Condition into new interface

This enables me to simplify SQLStore's definition (though this hasn't
been done yet) and also allows me to do non-store implementations of the
interface (such as a modifier)
Simplifies SQLStore as promised in 417c85d5
Cleans up Modifier\Storable (a bit)

Some unnecessary code was removed, including a number of un-used functions
(one of which was for user code, but other user code will soon be provided
in its place).

One of the functions was called from SQLStore, so the call has been
replaced by other code that does the same thing and does not need a
seperate function.
Removed unused array from UpdateConditionWriter

The array was checked for the existence of a key, initialized empty and
merged with the same array from sub writers, but never was an element
added to it.
Removed the concept "fieldnumber" from SQL writers

This was used solely for the storing and retrieving of joins. It was
rather contrived because it counted all the reference field, but not the
non-reference fields.

Now, we just use the fieldname instead, it is just as unique, it is less
contrived and it can also be used in places where we do not know which
field is a reference and which is not.
Removed double field/tablenamifying on Join array

This was being fieldnamified and tablenamified twice: once during creation
of the Join object and once when inserting the values in the SQL
statement. This isn't a problem at the moment, but when something like
table prefixes is added, it will suddenly start causing bugs.

I decided to remove the ifying when creating the Join object, because it
felt right to keep the "escaping" as close to the SQL as possible. In
addition, this makes it possible to use the join data when actually
interested in the type name, not the table name (such as when building a
Storable from the sql results).
Makes Store and SQLStore non-generated.

There were some reasons for having these classes, but it was better not to
generate outside the datatype classes.

This means a change in the public interface, as now we no longer have
separate insert and modifyAny function for each class, but just one
generalized version, which will detect the type automatically.

The creation of the Resolver class was moved to Modifier\Storable which
also means that the extraFiles mechanism is taken back into use.

The entire system that built objects upon Collection::getNext() had to be
remade and part of that change led to FieldDenamiefier (which isn't as bad
as it sounds, it uses a visitor-loop to see if the fieldnamified fiels are
in the original and if they are, recreates them in the output with the
untouched key, it doesn't actually try to reverse the namifying algorithm.

This closes #7.