* BBBikeTest: new test functions validate_bbbikecgires_yaml_string,
  validate_bbbikecgires_json_string, validate_bbbikecgires_data

  Also rewrote the validation function in t/cgi.t to use the new
  validate_bbbikecgires_data.
* cgi.t: use the json/yaml validation functions
* added at least one traffic light to the data-test directory
* bbbike.cgi: off-by-one error

  Routes with just two points in the path did not had a
  direction entry. This is now fixed.
* cgi: harmonization of json/yaml/xml outputs

  AffectingBlockings are restricted now to just five subfields (added
  "Recurring" to the xml output, removed the net/strassen objects and
  more fields from the json/yaml output).

  Also adapted the rnc schema: the subelements in AffectingBlockings
  may now be in any order, which is probably the reality if using
  XML::Simple, and added the new field.

  The kwalify schema has the AffectingBlockings field better
  documented; it's not just "type: any" anymore.
* t/cgi-test.t: added some json tests
* cgi: added LongLatCoord field for yaml/json/xml output

  Same as Coord (which was anyway marked with "don't use"), but with
  WGS84 coordinates. Requested by Dennis.
* fix for CGI.pm's charset problem (CPAN RT #67100)

  Some current CGI.pm version (e.g. 3.63) always set
  charset=iso-8859-1 in the content-type header, even for non-text
  types like image/* and application/*. To fix this, everywhere
  charset is explicitely set to the empty string.

  To test this, all test scripts which expect non-text content types
  are not anymore using $resp->content_type, because this is not
  returning the charset attribute. Instead
  $resp->header('content-type') is used, which returns the raw http
  header value.

  For the discussion of the CGI.pm bug, see
  https://rt.cpan.org/Ticket/Display.html?id=67100
* data update