framework/summary.py: Replace Section heading with docstrings

The sections headings are not really that useful, but they might as well
be kept as class level docstrings instead of being thrown away.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
framework/summary.py: Adds new summary class and two support classes

This new summary class (currently NewSummary), is a complete redesign of
the summary generation system. Much of the code in summary was not
commented, and also not clear as to what it was doing, making it very
difficult to maintain and even more difficult to improve. The other
problem with the code was architecturally it was clobbered together,
doing some of the work in the summary.py file, and some of the work in
the piglit-summary-html.py file.

The new summary class does all of it's work in the summary.py file, and
from an API point of view, in one class. The summary class uses it's
constructor to build lists of passes, failures, skips, problems, etc.
and then uses methods to generate output. The reference implementation
of that kind of method is for generating HTML, but in theory it could be
used to generate anything: XML, CSV lists, printed lists ala
piglit-summary, etc.

Also updates the .gitignore file to ignore some generated content
created by this class.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
templates: adds mako templates for new summary code

Adds the actual templates used to by the new mako based summary code.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
piglit-summary-py: Use the new summary class to generate HTML

Replaces all of the original summary generation code with new summary
generation code.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
templates: Remove old HTML templates

These template files are no longer used, and so they should be removed.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>
framework/summary.py: Build subdirectories for subtest result pages

This patch changes the generation of HTML summaries such that test
result pages are put in sub-directories (ie. spec/GLSL 1.0/foo/bar.html)
Otherwise 10,000+ HTML files are placed in a single folder, which is
really ugly and hard to find.

Signed-off-by: Dylan Baker <baker.dylan.c@gmail.com>