Phing  and build.xml updates

The build.xml in the root should be able to be used to build the component.

I figure the build folder can be used for the packaged component.

I'm not sure if we should store the phpdoc, component and packages (com_biblestudy, mod_biblestudy, etc), and all the reports generated by **phing** on github. We should talk about this, since those things will change very frequently, so we may not need to keep track of them.

Having said that, this commit is without those files. If we decide to include them, we can just run **phing package**, **phing apidoc**, etc. to generate them.

Not all targets are working in phing, **php phpunit**, for example, doesn't work yet since I believe we're in the early stages of creating unit tests for the component.

Lastly, the build status of the component will always display on the main project page on github. Each time there is commit to the main repository, it will automatically run **phing build**, which runs all of the code analyzers against the component.