Workaround for fragment encoding of eMAID type (based on OpenV2G templates)

[andcaspe]

Describe your changes

I’ve recently run into the same problem reported here with fragment encoding of the eMAID / EMAIDType. Specifically, the EXI stream produced by Josev does not match what the autogenerated code produces, causing interoperability issues.

I explored possible solutions and ended up implementing a workaround inspired by how OpenV2G handles it.

Instead of resolving the EXI grammar issue directly (which I understand is quite complex), I chose the following workaround:

• Defined static templates where the OpenV2G–autogenerated code is placed.
• Made the eMAID type reference these templates when generating fragments.

This is essentially a copy/paste of OpenV2G’s solution into the autogenerated code, so it doesn’t fully fix the root cause at the grammar level. But it does align the output with the expected EXI stream and passes interoperability checks

Issue ticket number and link

Refer to #60

In addition, I have tested this solution on the following branch, where I have defined a new test case of eMAIDtype:

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• I read the contribution documentation and made sure that my changes meet its requirements