realize p2p transaction using thirdparty-scheme-adapter - PISP side

[eoln]

Goal:

As a Developer
I want to apply the same patterns to all parts of the code (with thirdparty-scheme-adapter)
so that we can effectively work and build the codebase

Acceptance Criteria:

• PISPTransactionModel refactored to newest API changes
• integration test

Complexity: Medium> there is already POC code
Uncertainty: Low > there is already POC code

---

Tasks:

• update dependencies
• update docker images to use latest
• http-request base class refactor
• reexport Typescript interfaces for sdk-scheme-adapter API so thridparty-scheme-adapter can use them
• publish sdk-scheme-adapter to npm so can be used as dep by thirdparty-scheme-adapter
• fixing sdk-scheme-adapter npm installation problem
• fixing export of Typescript in api-sinippets
• reexport Typescript interfaces for sdk-standard-components from api-snippets types
• prepare P2PTransaction detailed UML sequence
• migrate DeferredJob from sdk-scheme-adapter
• fix/update api-snippets autogenerated files & drop hello example endpoint
• fix publish CI step dependency for thirdparty-scheme-adapter
• fix UnresolvedPromiseWarning in outbound/authorizations.model.test
• migrate Async2SyncModel from sdk-scheme-adapter
• expose sync patchThirdpartyRequestsTransaction endpoint
• integration tests for SDKOutgoingRequests.requestPartiesInformation
• sdk/pisp/dfsp backend request classes
• change in design: propagate interface changes of POST /thridpartyRequests/transactions payload -> api-snippets
• PISPTransactionModel refactor - use api-snippets for partyLookup endpoint @ Outbound
• PISPTransactionModel refactor - use new payload to call /thridpartyRequests/transactions
• PISPTransactionModel refactor - use of deferredJob
• PISPTransactionModel feat - calculate timeout for each deferred job from expiration field send in initiate step (will be covered in another story)
• PISPTransactionModel feat - two step hazard mitigation
• improve unit tests to reach the coverage
• integration test

Done

• Acceptance Criteria pass
• Designs are up-to date
• Unit Tests pass
• Integration Tests pass
• Code Style & Coverage meets standards
• Changes made to config (default.json) are broadcast to team and follow-up tasks added to update helm charts and other deployment config.
• TBD

Pull Requests:

• chore: update deps & audit-resolve thirdparty-sdk#47
• chore: 2060 latest docker images thirdparty-sdk#48
• feat: introduce shared/http-request base class thirdparty-sdk#49
• feat: 2060 api typescript sdk-scheme-adapter#255
• refactor: drop using internal modules sdk-scheme-adapter#258
• https://github.com/mojaloop/api-snippets/pull/56/files
• chore: move api-snipptes to dev deps sdk-standard-components#128
• docs: P2PTransaction sequence diagram thirdparty-sdk#50
• feat: defferedJob thirdparty-sdk#53
• fix: update generated files api-snippets#60
• fix: 2060 api templates generation warning and drop hello example endpoint thirdparty-sdk#55
• ci: add build-local dep to publish step thirdparty-sdk#57
• feat: 2060 separate backend requests and sdk requests thirdparty-sdk#59
• fix: unresolved promise warning in authorization model thirdparty-sdk#62
• feat: 2060 async2sync model thirdparty-sdk#63
• feat: patchThirdpartyRequestsTransaction sdk-standard-components#134
• refactor: 2060 remove notifyThirdpartyAboutTransfer  thirdparty-sdk#64
• test: integration of requestPartiesInformation thirdparty-sdk#65
• refactor: 2060 design change post thridpartyrequests transactions api-snippets#65
• feat: use api-snippets for partyLookup endpoint thirdparty-sdk#71
• refactor: 2060 pisp transaction model transaction request thirdparty-sdk#74
• refactor: 2060 use deferredJob in PISPTransactionModel thirdparty-sdk#76
• feat: 2060 hazard mitigation thirdparty-sdk#77

Follow-up:

• (realize p2p transaction using thirdparty-scheme-adapter - DFSP side #2108)

Dependencies:

• N/A

Accountability:

• Owner: TBC
• QA/Review: TBC

[lewisdaly]

I'm not sure where this belongs, but there is no handler for PATCH /thirdpartyRequests/{id} in the thirdparty-api-adapter. @eoln should this be a part of this ticket or (my preference) another?

[lewisdaly]

I'm also realising that that call is in the API draft but not the latest sequences... my bad :(.

[eoln]

@lewisdaly PATCH is used by DFSPTransitionModel so I added this as task to (#2108)