Consider specifying what should happen when sending a `request` with `path-with-query: none` and `authority` set

In the case of path-with-query, the spec defines none as:

When none, this represents an empty Path and empty Query.

This suggests that none and some("") denote the same state. However, by writing tests for client.send, they resolve differently (using wasmtime v46)

• send with set-path-with-query(none), returns Err(HTTP-request-URI-invalid)
• send with set-path-with-query(some("")), returns 200, since some(""), resolves as /

Given the definition above, the natural expectation is that none is handled the same way as ""; however, given the current mismatch in behavior, I think it's worth clarifying in the spec:

• The meaning of none for path-with-query and the resolution mechanism.
• The relationship with authority: the spec does not define the validity of path-with-query relative to the presence of authority, however, some implementations do (e.g., https://github.com/bytecodealliance/wasmtime/blob/main/crates/wasi-http/src/p3/request.rs#L337)

Related:

• https://github.com/WebAssembly/WASI/issues/780
• https://github.com/bytecodealliance/wasmtime/issues/11780

Start with the path-with-query definition and the client.send behavior described in the issue, then compare the Wasmtime implementation at crates/wasi-http/src/p3/request.rs with related issues 780 and 11780. Done means the specification clearly defines none, its resolution with authority, and the expected validity and request behavior.