rtspsrc: Don't replace 404 errors with "no auth protocol found"
When getting a "404 Not Found" response from the DESCRIBE request, the source produced a "No supported authentication protocol was found" error instead of passing on the 404, which was confusing.
Only produce this error message when we're handling a response of "401 Unauthorized" without a compatible WWW-Authenticate header.