Fix adjoint validation with global measurements

[dwierichs]

Context:
Validation of the adjoint method did not take device wires into account, leading to the linked issue.

Description of the Change:
Include validate_device_wires in _supports_adjoint in DefaultQubit.

Benefits:

Possible Drawbacks:

Related GitHub Issues:
fixes #5760

[sc-64278]

[albi3ro]

Potentially we could add a device_wires keyword argument to adjoint_state_measurements, and then pass in device_wires or adjoint_state_measurements to the StateMP. And if both are None, maybe we just default to one qubit?

While this would work for the validation, would it actually work for the execution part?

[dwierichs]

Is the current approach not a good idea? Note that the execution is not affected by the bug, it's just the validation, because it calls _add_adjoint_transforms(prog) before using the device wire validation to update the global measurement types.

[albi3ro]

Ignore earlier comment. This seems to be a perfectly straightforward fix that gets the job done :)

[PietropaoloFrisoni]

Thanks @dwierichs , LGTM!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.66%. Comparing base (f5b805b) to head (ea30d1c).
Report is 270 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5761      +/-   ##
==========================================
- Coverage   99.67%   99.66%   -0.02%     
==========================================
  Files         416      413       -3     
  Lines       38686    38813     +127     
==========================================
+ Hits        38562    38684     +122     
- Misses        124      129       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.