Fixes #10 - performance improvement listing time entries

Previously, was making a separate API call to look up the project during each print_time_entries. Now moved to making the project call at the same time as the time_entry call and matching the time entries project id to the project when building the entry to print.

Time tests

I have 8 time entries in my current dataset. So, for each one it has to call the projects API in the prior version.

Prior version elapsed time: 9.55 seconds
New version elapsed time: 2.42 seconds