URI reference "/:" misinterpreted to have schemeless path

[yescallop]

The string "/:" should be a valid URI reference with only a path according to RFC 3986, but parsing it with uriparse results in an error "schemeless path URI reference starts with colon segment". This case was found when fuzzing fluent-uri against this crate.