Address redundancy of overall_results html templates

[blreams]

When I was working on Issue #123, I figured out that there was a good bit of redundancy in the following templates:

• overall_enter_picks_results.html
• overall_final_results.html
• overall_week_final_results.html
• overall_week_not_started_results.html

I figured that I could combine all four of those templates into a single template and use the context variable pool_state to render appropriately within the template. The reason for such a change is twofold:

1. It will make it easier to incorporate the jquery tablesorter if it only has to be applied in a single template.
2. It follows from the python DRY (Don't Repeat Yourself) principle.

I have a commit ready to go for this issue.

[blreams]

I am making similar changes to the following week results templates:

• week_final_results.html
• week_in_progress_results.html
• week_not_started_results.html

These three templates are replaced by a single template named week_results_combined.html. In this template I am using a new context variable week_state to render the page appropriately based on the state of the week.

One other note...in these combined templates, I am removing the "dummy" <td> tags that served to create line separators between table rows. Instead, the same effect can be created by adding border-bottom css attributes to each of the actual row <td> elements. This is necessary because the table sorter would have separated out all those empty <td> tags upon sorting.

[blreams]

Deployed to pythonanywhere, closing this issue.