Feature/ps2 139 support for emandate cancelmandate

[Rhesa-Buckaroo]

No description provided.

[Rhesa-Buckaroo]

I found a blocking regression in this PR.

ConfiguredTransaction.EMandate() now returns new EMandateRequestObject() without any configured request attached, while EMandateRequestObject only operates on ConfiguredDataRequest. That means existing transaction-based call chains like .TransactionRequest().SetBasicFields(...).EMandate().CreateMandate(...) will now fail at runtime when the implementation reaches this.ConfiguredDataRequest.BaseDataRequest.

This effectively changes the service from transaction-based to data-request-only, but the transaction entry point is still exposed. I’d recommend either:

• restoring the transaction-backed constructor/path, or
• removing the transaction entry point entirely in the same change and documenting it as a breaking API change.

As it stands, this looks like a runtime-breaking regression for existing SDK consumers.