[E-Documents Core] - Enabling remittance advice export via E-Documents (payment journal + posted payments)

[AndriusAndrulevicius]

Implementation

Adds an electronic counterpart to BC's existing paper remittance advice reports: a new "Create E-Documents" checkbox on reports 399 ("Remittance Advice - Journal") and 400 ("Remittance Advice - Entries") creates E-Document records of a new "Remittance Advice" type that flow through the standard E-Documents engine and export as UBL 2.1 RemittanceAdvice XML via the PEPPOL BIS 3.0 format.

Key additions:

• Adds a new "Remittance Advice" E-Document type (enum 6121) with its own data-assembly, validation, and export path in E-Documents Core, reusing the existing service/format/workflow engine (no new dependencies).
• Adds report extensions on 399 (unposted payment journal) and 400 (posted Vendor Ledger Entries) with an opt-in checkbox that collects payment/applied-document data and creates one E-Document per payment.
• Ports report 399/400's allocation, currency-conversion, and payment-discount math into a shared assembly codeunit so the E-Document data matches the printed report exactly.
• Adds a PEPPOL BIS 3.0 format implementation that generates UBL 2.1 RemittanceAdvice XML (header, accounting parties, payment means, one RemittanceAdviceLine per applied document).
• Adds a non-editable "created" flag on Gen. Journal Line with a Void action (clears the flag / cancels the E-Document) and an Open E-Document action on the Payment Journal page.
• Re-points the E-Document from the journal line to the posted payment Vendor Ledger Entry at posting time (journal lines are deleted on posting), with a delete-safety subscriber that cancels orphaned E-Documents if a flagged, un-re-pointed line is removed before posting.
• Moves the existing UKSendRemittanceAdvice "send by email" actions natively into BaseApp (VendorLedgerEntries.Page.al, PaymentJournal.Page.al) and marks the old UKSendRemittanceAdvice page extensions obsolete — this is a code-location move only, the email-send behavior itself is unchanged and does not route through the new E-Document type.
• Adds test coverage (EDocRemitAdviceTest, 13 scenarios) for journal/entries happy paths, multi-line/multi-vendor grouping, credit memos and payment discounts, duplicate/re-export confirms, posting re-point, void, and format extensibility.

Linked work

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.