Project architecture refactoring

Salam Walid,

In this pull-request you'll find that I did re-organize the whole project to conform with [maven standard directory layout](http://fusesource.com/docs/esb/4.2/deploy_osgi/Build-MavenDir.html), then I moved all pacages to `org.alfanous` following Java's naming conventions. So importing for other packages in source code should now be 
```java 
import org.alfanous.package.Class;
```

this transition is important as it allow as to:
* generate jar files easily and automate the build process
* easily generate documentation
* upload the library to [maven central repository](http://mvnrepository.com/) when it's ready, to make it to other projects to download and use the Jar file.
* easily run the unit tests with junit
* generate ant build files

aside that, I added a `.gitignore` file to ignore tracking unnecessary files, updated the README files with useful information, and renamed the `Error` Class to `StatusMessage` as it conflicts with the Java's standard library `java.lang.Error`

Thanks, and keep up the good work (Y)