feat(vehicle): add support for LeapMotor API

[syphernl]

Summary

Adds support for the LeapMotor API (used by the official mobile app).

There is currently no public API, but the community has reverse-engineered the API used by the app:

• https://github.com/kerniger/leapmotor-ha
• https://github.com/markoceri/leapmotor-api

This integration enables EVCC to retrieve key vehicle data such as SoC and cable connection status.

Certificate requirements

The API requires app-level mTLS client certificate material (app_cert.pem and app_key.pem).

These files are not provided and are not automatically retrieved.

Publishing or distributing such credentials would expose reusable authentication material.
Users must supply their own legitimate certificate material.

There is currently no official or user-friendly way to obtain these certificates.

Community resources may discuss possible approaches or compatible material, but users are responsible for reviewing and deciding whether such methods are appropriate for their setup.

Security / scope notes

• This PR contains integration code only (no APKs, extracted assets, or credentials)
• No secrets, tokens, certificates, or traffic captures are included
• Intended for use with the user’s own account and vehicle

Caveats

• Relies on an unofficial, reverse-engineered API
• May break if Leapmotor changes the API or authentication flow
• Requires external certificate material not covered here

Status

This PR is currently untested with a real vehicle, as I have not yet received mine. Leaving this as a draft until it can be validated in practice. Hopefully someone in the community is able to do so.

Todo

• Review and simplify the implementation where possible
• Test with real vehicles (e.g. T03, B10, C10)

Docs

Docs are being worked on in evcc-io/docs#1049

Help wanted

If you own a Leapmotor and can test this integration, feedback would be very helpful.

References

• Leapmotors Einbindung? #28084
• Leapmotor T03 #23583
• Generic car / manual SoC entry #26663