To avoid the problem of differnt versions of P6 and not being able
to connect to them, we make use of CSV files.  At this stage we just
have skeleton that does nothing but verify a directory name and table is supplied.

The directory represents the databse.
Added some fixtures that I took from a P6 database.  Now we can load
activity codes, their values and load their children.  Most of this
is in CSVBase (not children) so should be a doddle to add other
tables.
added the console rake task so it all loads up
Decided to just put the BREBootstrap.xml and P6 api jar files in
lib/p6/api and lib/p6/api/lib respectively.  This means the P6
API environment is set up in p6.rb and there is no need for
lib/p6/config.rb so that and testing has been deleted.

I setup P6 in the directories above and it connects to a real P6 database
that might change once this fire is put out.

One side affect is the P6 API keeps things running so I have to CTRL + C
to stop it.
Just added ability to get the database id given the name.
Changed P6::Session to P6::P6 which then involved all sorts of other
changes to get rid of  P6::
Placed the QGC specific migration code under git at the point where
there is a skeleton that does nothing but load the CSV tables and loops
through CSVActivityCode.
in the middle of a big ball of mud because I didn't commit
The deletion of what I attempted to migrate before now works.
Finally sorted out the activity code hiaerarchy.

This is now the proper base from which to make changes and improve this massively.