Combine Authorise, AuthoriseEncrypted and Authorise3D structures

[zhutik]

Currently, all Authorise, AuthoriseEncrypted and Authorise3D structures are used, but they are 95% identical.

AuthoriseEncrypted will be removed, "additionalData" field will be added to Authorise structure.
AuthoriseEncrypted method is Payment Gateway will be removed.
Authorise3D structure will be removed
Authorise3D method will be removed

[jvalecillos]

Hello @zhutik, I'm currently working on adding new endpoints to the existing library and I just found out this issue about the duplicated structs and methods for payment authorization requests. There are even more gains about combining the methods, namely: supporting other payment methods.

My problem was: What about if other people is using these methods already?. So, my idea doing this in several steps:

1. Combining the request struct in only one, and then the AuthoriseEncrypted, Authorise3D are just aliases of Authorise but adding a note about they are deprecated.
2. In the same way the structs AuthoriseEncrypted and Authorise3D just embed a general Authorise.
3. Finally, the methods and the duplicated structs are deleted altogether and increase a major version of the library.

Let me know your opinion.