[E-Documents Core] - Email Reminder/Fin. Charge Memo E-Document

[GMatuleviciute]

This pull request does not have a related issue as it's part of the delivery for development agreed directly with @altotovi @Groenbech96

Implementation

With this update E-Documents are automatically created and emailed, when Issuing Reminders and Finance Charge Memos.

When the user clicks "Issue" action on the Reminder:

1. If they click OK without selecting an option in the "Print" field, the Reminder is issued, an E-Document is created and sent via the integrated service.
2. If they choose Print-> Email, the Reminder is issued, an E-Document is created, it is sent via the integrated service and email is sent with the E-Document attached.

When the user clicks "Issue" action on the Finance Charge Memo, exactly the same process happens as described above:

1. If they click OK without selecting an option in the "Print" field, the Finance Charge Memo is issued, an E-Document is created and sent via the integrated service.
2. If they choose Print-> Email, the Finance Charge Memo is issued, an E-Document is created, it is sent via the integrated service and email is sent with the E-Document attached.

Two new actions were added to "E-Document" Action Group in the Issued Reminder:

• Create and Send E-Document: Creates an E-Document from the issued Reminder and sends it via integrated service.
• Create and E-mail E-Document: Executes the same action as above, with an additional step to send an email containing the E-Document as an attachment.

The same new actions were added to "E-Document" Action Group in Issued Finance Charge:

• Create and Send E-Document: Creates an E-Document from the issued Finance Charge Memo and sends it via integrated service.
• Create and E-mail E-Document: Executes the same action as above, with an additional step to send an email with attached E-Document.

This update adds full E-Document support for Issued Reminders and Issued Finance Charge Memos, ensuring they meet Peppol standards while keeping financial document processing consistent.

Fixes #

[github-actions]

Could not find linked issues in the pull request description. Please make sure the pull request description contains a line that contains 'Fixes #' followed by the issue number being fixed. Use that pattern for every issue you want to link.