Validate that resources belong to the right device.

[nical]

Checklist

• Run cargo clippy.
• Add change to CHANGELOG.md. See simple instructions inside file.

Connections

Fixes #3927

Description

A pretty boring and mechanical change set although fairly important for the browser use case. Each entry point that takes resources as input must check that these resources are associated with the same device.

I'm sure that I have forgotten some, thankfully it looks like the CTS is rather thorough about testing this so we'll see what's missing when this makes its way into firefox.

Testing

I enabled the the device_msimatch test which I added when filing the issue. It only covers a tiny portion of the cases but the CTS has good coverage of this so adding exhaustive tests here is not as important.

[ErichDonGubler]

These changes LGTM. I'm paranoid and want to make sure we cover all of the API that's necessary, but I guess that need not block. We can keep iterating and covering more cases with follow-up work.

[cwfitzgerald]

In the future, I think it would be nice to have a trait like

trait DeviceChild {
    fn get_device_id(&self) -> ....;
    
    fn is_child_of(&self, device: Id<Device>) -> Result<(), DeviceError> {
        ....
    }
}

or something to streamline this a bit and prevent mistakes, but for now this is fine.