Look into how we can not trigger CopayNotifications::NewStatementNotificationJob until we can enable that feature again

[digitaldrk]

Issue Description

Given: We are not sending new statement notifications
When: the CopayNotifications::NewStatementNotificationJob could possibly get triggered
Then: We won't initialize the job causing them to accumulate

Tasks

• Remove call to CopayNotifications::NewStatementNotificationJob until we want that feature back
• Possibly remove the call to ParseNewStatementsJob which calls the new statement notification job

Design and Front End sync on implementation of design

• Required
• Complete
• Not Required

Acceptance Criteria

• We comment out the job(s) mentioned above in a PR to stop unnecessary jobs from being run

Testing

• N/A if non development work
• Testing passed and documented in this ticket based off the "Then" statement in the description

Test procedures:
If additional testing steps or credentials to perform testing are needed list them here

Ticket Creation - Definition of Ready

Ticket requirements

• Description written
• Tasks defined
• Acceptance criteria written
• Testing defined
• Add Labels
• Assign Type
• Assign Priority (Normal = Medium)
• Assign Group(s)
• Assign to a Project
• Attach to an Parent Epic
• Estimate Points