clockingit : add hourly rate to users and reports

Create a patch to the latest development repository of clockingit (see instructions at [login to view URL]:index) to implement the feature described below: [login to view URL]:rate Each participant in a project can set an hourly rate. In the reports, the number of hours worked are multiplied by the hourly rate and shown next to the total and sub totals. * There can be only one hourly rate per user per company, accross all projects (because the hourly rate may vary when providing services to a non profit or to a large corporation) * The hourly rate is defined by the user in the user preferences, for each known company and the default hourly rate is null * Each hourly rate is associated with a localizable currency symbol * The hourly rate is a public information available to all users * The hourly rate only shows in the reports * In each report, a price column or line is added whenever a time is shown * The value of the price cell next to a time cell is the agregated sum of the time spent by each participant weighted by their hourly rate The patch must be submitted to the clockingit authors on [login to view URL] and meet their standards so that it can be approved and commited to the mainstream version. The patch must also be applied to the latest version published on clockingit.com. A virtual machine with said version will be provided. A modified virtual machine with the patch applied must be delivered. It must be possible to run all the tests with rake test on the same virtual machine. ## Deliverables A1) Complete and precise implementation of the description of the bid request. A2) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. A3) Buyer will receive exclusive and complete copyrights to all work purchased. A4) Software must be platform, browser and os independent. A5) Software must be provided with a git repository initialized when the work started (typically by unarchiving the sources and running git init + git commit at the toplevel) A6) The work must be commited under git on a daily basis. A7) The reason for each change (not the change itself) must be explained in the ChangeLog file at the root the package tree. M1) All lines modified must be executed by the tests run with rake test. R1) A set of unit tests covering 100% of the code written or modified for the job. There is no need to cover the code that already existed and that was not modified. R2) a single command without argument must run all the unit tests, report the total percentage of coverage and list all the lines of code (either python, ruby, c, c++, javascript or java) that are not covered. R3) Implement a verbose mode for running the tests so identifying which unit test fails and why is straightforward. ## Platform GNU/Linux