In this PR:

• The original code has several units included on the uses clause of most of the units that are not needed, and they make it for a bloated and in cases (with C++Builder specially) not working units for the client code.
• The StampRequest was storing the passed CFDI into a "temporary" file, saved to the current directory. This won't work in lots of cases, for instance, if the user doesn't have privileges to modify the current folder (which will be the case for a lot of users as the application folders should not be modified in general without privileges), or there are several concurrent users that need to use this services at the same time. The fix was to just pass the XML in memory, instead of storing it into disk and then reading it again.
• A new property for the Cancellation response to store the original JSON value, as that class is not parsing correctly the uuid field in the response because that property is a dynamic key (the UUID is the key) so the RTTI can't automatically parse this. This has been reported to SmarterWeb with case MDA-68926