[W1][Codeunit][8900][Email Impl] SourceRecordRef.ReadPermission() condition was removed from FilterRemovedSourceRecords-procedure. Fixes AB#8635

[dkastena]

What & why

If at least one security filter is applied to the “Purchase Header” table, the user will have a problem when pushing the 'Add file from source document’ action on the “Email Attachments” subpage.
Result:
Message: "Did not find any attachments related to this email"
Expected result:
The page should show the list of attachments from the source purchase document. Like it works without applying security filters.

Linked work

Fixes AB#8635

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 (required — be specific: scenarios, commands, screenshots for UI changes)

GetBySystemId() already respects the user's security filter.
The blanket ReadPermission() check was the real problem because it:

• Bypasses fine-grained filters the admin set up
• Acts as an all-or-nothing gate instead of respecting row-level filtering
• Prevents filtered access even when the user should see specific records

By removing it, we let GetBySystemId() do what it's designed to do—check permissions filter-aware.

Risk & compatibility