Track PL new stateprep error message

[paul0403]

Context:
PL recently changed error messages for bad stateprep/basisstate use cases (PennyLaneAI/pennylane#6021).
We update our tests to agree with them.

Benefits: Frontend tests test_skip_initial_stateprep/TestPossibleErrors can pass

[github-actions]

Hello. You may have forgotten to update the changelog!
Please edit doc/changelog.md on your branch 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.

[rmoyard]

Thanks @paul0403 !

[dime10]

You're PR needs to update the PL ref to the commit (technically package version) that introduced this new behaviour no? Or is the dev build we're tracking already newer?

[dime10]

I'm guessing the kokkos failure is addressed by your other PR? Happy to overwrite the merge if so

[paul0403]

I'm guessing the kokkos failure is addressed by your other PR? Happy to overwrite the merge if so

Seems like it: wires must take values lower than the number of qubits. likely came from the wire argument seeing [2,3] instead of [0,1] due to not reading the qubit manager map values.

Kokkos failure is because the kokkos version (dev50) is before the lightning PR where this got fixed in kokkos. The lightning PR is merged into lighting rc (PennyLaneAI/pennylane-lightning#869) and hence does not have a dev version bump. We can overwrite merge and rcrcrc should pass (or if it fails, not with the stateprep errors).

Alternatively, I can open another PR in lightning and merge the kokkos changes into lightning's master, and track the bumped lightning dev version.

Alternatively alternatively, we can wait for lightning to merge something into their master to trigger a dev bump, and we track that.