validate content-length is decimal digits in wasi-http

[netliomax25-code]

1. get_content_length and the p3 parse_header_value read Content-Length with u64's FromStr, which also accepts a leading +, so a value like +5 is parsed as 5.
2. RFC 9110 defines the field value as 1*DIGIT, so a value like that is accepted here while a strict parser (a proxy or the peer) would reject it. The parsed value drives the p2 and p3 request/response body framing, and parse_header_value runs when a guest builds a field map.

Reject any content-length value that is not a non-empty run of ASCII decimal digits before parsing, at both sites. Added unit tests covering +5, -5, a leading space, and the empty value.