cam: Properly mask out the status bits to get completion code

[imp]

Summary

ccb_h.status has two parts: the actual status and some addition bits to
indicate additional information. It must be masked before comparing
against completion codes. Add new inline function cam_ccb_success to
simplify this to test whether or not the request succeeded. Most of the
code already does this, but a few places don't (the rest likely should
be converted to use cam_ccb_status and/or cam_ccb_success, but that's
for another day). This caused at least one bug in recognizing devices
behind a SATA port multiplexer.

PR: 270459
Sponsored by: Netflix

[mav]

The additional flags are normally used only for queued requests. So some of places here are likely not affected. But it should not harm probably any way.

[ken]

Looks ok to me.

[imp]

In D39572#900813, @mav wrote:

The additional flags are normally used only for queued requests. So some of places here are likely not affected. But it should not harm probably any way.

I agree. IMHO, it's better to have a more foolproof and simpler rule to follow than to do some things one way and other things another.
The path inq commands can't really ever fail... The few SIMs I looked at all unconditionally returned CAM_REQ_CMP anyway...
But surprisingly these were the few places that checked the status w/o masking and I thought it best just to do them all.
But I think 3 or 4 of them may have been doing it wrong (the nvme one was fixed after the tree I did these changes in,
btw). If there were a bunch more, I'd likely split things up differently.