File component attachments are cached during notification sending

[hlayisanimazuze]

From the configurations used (link to configurations), the file component exhibits unexpected behavior based on the presence or absence of {data.recipient.id}:

If {data.recipient.id} is removed, the notification sends out the previous attachment instead of failing or clearing the attachment.
If {data.recipient.id} is present, it pills the previously sent attachment to the user

Steps to reproduce the behavior:

1. Go to 'https://functional-adminportal-test.azurewebsites.net/dynamic/Shesha/notifications'
2. Click on 'Send'
3. Select your recipient, on notification type use Health Awareness, attach files then select email channel. Then send the email
4. Immediately, click the send button again and select the same recipient you used the first time
5. Actual Results: Immediately after selecting the recipient, the file previously sent, gets pulled

Steps to reproduce the behavior:

1. Navigate to the send notification designer form: https://functional-adminportal-test.azurewebsites.net/shesha/forms-designer?id=f6e975e6-05e5-4af6-b056-05e556a2ee0f
2. Click on 'file list' component and remove the value on Owner ID
3. Save changes, then send the notification with a different attachment
4. Afterwards, check the nofification received on your email and confirm whether the attachment is the same or not
5. Actual Results: The attachment showing is the previous one sent

Expected behavior
The system should not cache or send outdated attachment