Include results on tracker for default.qubit

[lillian542]

DQL included results in the tracker, DQ2 currently does not. Results for each call of execute added here.

[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.

[lillian542]

From the perspective of a user this just makes default.qubit keeps doing a thing that it already did already, so I didn't add a changelog entry for this one

[codecov]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (751400d) 99.63% compared to head (110a895) 99.63%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4649   +/-   ##
=======================================
  Coverage   99.63%   99.63%           
=======================================
  Files         376      376           
  Lines       33647    33648    +1     
=======================================
+ Hits        33523    33524    +1     
  Misses        124      124           

Files	Coverage Δ
pennylane/devices/default_qubit.py	100.00% <100.00%> (ø)

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

[lillian542]

[sc-46914]

[albi3ro]

We can probably just update the changelog entry that's already about the tracker:

* `default.qubit` now tracks the number of equivalent qpu executions and total shots
  when the device is sampling. Note that `"simulations"` denotes the number of simulation passes, where as
  `"executions"` denotes how many different computational bases need to be sampled in.
  [(#4628)](https://github.com/PennyLaneAI/pennylane/pull/4628)

But after adding this PR to that entry, I'd be happy to approve.