Investigate Settlements API failure

[rmothilal]

Priority: High
Investigate why the central-settlements API crashed on Kubernetes.
you search should relook at getWindowsBySettlementIdAndParticipantId function in src/models/settlement/facade.js

Tasks:

• Run local instance of the environment to be able to test based on @mdebarros 's video https://drive.google.com/file/d/1HHuszQ3bjSTbXKujf6h0JkmYBW2K0HKD/view [@vgenev]
• Fix logging of errors [@vgenev]
• Put logging throughout the settlements API [@vgenev]
• Investigate the suggested method behavior [@vgenev]
• Fix any unwanted behavior [@vgenev]
• Fix unit tests of the the above fixes [@vgenev]
• Make coverage 100% again [@vgenev]
• Run postman tests for few hours without restarting [@vgenev]
• transfer.prepare
• transfer.fulfil
• close settlementWindow
• trigger settlement event
• settle the accounts
• all available for the Settlement API GETs
• with delay slightly bigger than the enum cache
• repeat

Acceptance criteria:

• log requests [@vgenev]
• log responses [@vgenev]
• catch all the errors [@vgenev]
• log all the errors [@vgenev]
• tests running without errors [@vgenev]
• coverage is 100% [@vgenev]

PRs:

• Feature/#454 investigate settlements api failure central-settlement#33

Accountability:

• Owner [@vgenev]
• QA/Review [@rmothilal]