Include test suite results for validator implementations

[awwright]

It might be useful if we include a brief summary of what features different validators support, and indicate test suite compliance.

This might be a task better handled by someone else, though.

[Relequestual]

Further specification needed.

[awwright]

I'm not really sure what I was thinking, but lemme guess

[adamvoss]

Ideally, the test suite would produce a machine readable report (YAML, JSON, or CSV) which could be added within _data and then displayed on the website in a similar manner as used in json-schema-org/json-schema-org.github.io#131.

Perhaps too high of barrier to entry, but this could even be automated in separate repository where all implementations to be listed had to include code that boot-strapped testing their library against the suite and generating the report.

[Relequestual]

Looking at shields.io, jenkins is the only one to support number of tests passed.
We could say we only display build status for projects which use at least the official test suite.

[gregsdennis]

I think Bowtie properly covers this. It doesn't yet have all of the implementations, but the framework is there.

[benjagm]

We'll have this covered in the new version of the implenmeters page #160

Closed in favour of #160