Draft: Introduce Electronic Invoice item and SuperPDP connector
This will be used on Nexedi ERP5 starting next week. I will have to write some code as we go, but the overall model should stay. There are three important decisions in my opinion:
- use custom items (and module) to store raw JSON/XML/whatever returned by the platform;
- items are used as a reference point to communicate with API, they generate an "real" Invoice transaction based on connector-dependant code, and their workflow get updated as this real Invoice evolves (mostly, because we want to handle rejection);
- separate the connector logic from the "generic" part, which is why there are two new BTs.
Mostly anything outside of these points is WIP, especially parsing, I do not want to write too much until we start seeing some real invoices. Note that only Purchase (incoming) Invoices are handled for now. I do intend to merge at some point, but now it is too early, so I did no cleanup at all.