[28.x][Payables Agent] Users can personalize-in the Name column on the draft page

[Explorer986]

What & why

This change adds a read-only Name column to the E-Document purchase draft lines subform (page 6183 E-Doc. Purchase Draft Subform). The column shows the name of the matched entity such as Item, G/L Account, or Resource, so reviewers can confirm a line was matched to the right record. It stays hidden by default and users personalize it into view. The value reflects the matched record rather than the extracted invoice description and cannot be edited.

Linked work

Fixes AB#641589

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome

• Built E-Document Core locally with no errors and no new analyzer warnings.
• Published to a local sandbox and opened the Purchase Document Draft page.
• Personalized the Name column into the Lines part and confirmed it shows the matched entity name, stays read-only, and updates when Type or No. change.
• Confirmed the column is blank for lines with no match and that it reflects the matched record rather than the edited Description.
• No automated tests added yet. The change is a small refactor of the existing SetDescriptionFromLineTypeNo behavior. I can add a codeunit test asserting GetMatchedEntityName returns the right value per line type if reviewers prefer.

Risk & compatibility

• Low risk. No table schema change and no new stored fields.
• The Name value binds to a page variable computed in OnAfterGetRecord, so there is no data upgrade impact.
• Existing description defaulting behaves the same because it now calls the shared GetMatchedEntityName helper.
• The new OnAfterGetMatchedEntityName integration event is additive for connector apps.