Fix error messages with program-capture device wires and shot vectors

[isaacdevlugt]

No description provided.

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/releases/changelog-dev.md with:

• A one-to-two sentence description of the change. You may include a small working example for new features.
• A link back to this PR.
• Your name (or GitHub username) in the contributors section.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.62%. Comparing base (743b3a5) to head (566c701).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7130   +/-   ##
=======================================
  Coverage   99.62%   99.62%           
=======================================
  Files         509      509           
  Lines       49599    49599           
=======================================
  Hits        49414    49414           
  Misses        185      185           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[isaacdevlugt]

@albi3ro are we missing tests here since the CI doesn't fail? 😅

[albi3ro]

@albi3ro are we missing tests here since the CI doesn't fail? 😅

I often just check for part of the message instead of the full thing. Error messages can sometimes get long, and we just want to check with enough detail to know it's error we wanted.

pennylane/tests/capture/workflow/test_capture_qnode.py

Line 54 in 2ef2af0

def test_error_if_shot_vector():

[isaacdevlugt]

@albi3ro thanks! makes sense :)

[AntonNI8]

LGTM