gobex: make connection id check less strict
gobex: make connection id check less strict

OBEX spec says:

  Only the first packet in the request needs to contain the Connection
  Id header...

  If a Connection Id header is received with an invalid connection
  identifier, it is recommended that the operation be rejected with the
  response code (0xD3) “Service Unavailable”.

Since not all requests packets need to contain Connection Id header we
should only try to validate it in case a header is received.

Reported by Hendrik Sattler <post@hendrik-sattler.de>

ComputeCycles/bluez,ComputeCycles/bluez,silent-snowman/bluez,silent-snowman/bluez,pstglia/external-bluetooth-bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,pkarasev3/bluez,silent-snowman/bluez,silent-snowman/bluez,pkarasev3/bluez,pkarasev3/bluez,mapfau/bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,ComputeCycles/bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,pkarasev3/bluez,ComputeCycles/bluez