feat: add Detailed Energy Use to drive-details

[jameskitt616]

Add Detailed Energy Use to Drive Details to fix #4375.

@swiffer ping

[netlify]

✅ Deploy Preview for teslamate ready!

Name	Link
🔨 Latest commit	59973f7
🔍 Latest deploy log	https://app.netlify.com/sites/teslamate/deploys/673b776a3da2270008fbed8b
😎 Deploy Preview	https://deploy-preview-4386--teslamate.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[swiffer]

Thanks for opening this PR - I do prefer getting #4367 in first.

This PR seems to be based on Grafana build bundled with TeslaMate v1.31.1, exports should be done on top of the latest master to avoid overwriting other changes / reduce noise from changed Grafana schema version.

To the added stats - as numbers are not fully matching and 10.6 kwh & 12.4 kwh are both referred to as "used" I would prefer changing that to Energy recovered and stop showing energy used before regenerative breaking. As the metric is new I've added a small explanation as well.

Commit that can be used after #4367 has been merged: 1b21cbb - feel free to use it for updating your PR if you agree.

[jameskitt616]

I copied your Updated file into the PR now.

[cschanzle]

Please use "braking" instead of "breaking".

[JakobLichterfeld]

I do prefer getting #4367 in first.

#4367 is merged

[swiffer]

@jameskitt616 - could you reset this branch to lastest master and include commit f71c965

(already including the change from "breaking" to "braking").

[jameskitt616]

Resolved the conflicts

[swiffer]

Thank you, would have been better to do a rebase instead to keep commits history clean but i think @JakobLichterfeld will do a squash merge anyhow.

[JakobLichterfeld]

but i think @JakobLichterfeld will do a squash merge anyhow.

In most cases yes. In #4367 it was by mistake.

[swiffer]

ready for merge with squash

[JakobLichterfeld]

lgtm, performance: instant on slow hw