Enhance createSettlementModels admin api endpoint to allow only pre-defined settlement models

[ggrg]

Goal:

As a Hub Operator
I want to be able to only define settlement models which could be mapped to real-world models
so that model definitions which don't make sense, fail upon creation attempt (e.g. DEFERRED/GROSS)

Notes:

• This story is good to have, but is not a priority for the current PI

Tasks:

• Create valid configuration matrix for settlement model properties: settlementGranularity, settlementInterchange, settlementDelay [@ggrg]
• Validate proposed configuration [@ggrg, @MichaelJBRichards]
• Implement validation and fail invalid combinations [@ggrg]
  • Update shared library [@ggrg]
  • Release shared library and implement in central-ledger admin api [@ggrg]
• central-ledger node upgrade (driven by @mojaloop libs upgrades)

Acceptance Criteria:

• Only valid settlement models can be added
• 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.

Pull Requests:

• feature/1210 Validate settlement model definition central-services-shared#180
• hotfix/Circular util/index module require central-services-shared#183
• feature/1210Validate Settlement Model Definition central-ledger#594

Follow-up:

• N/A

Dependencies:

• N/A

Accountability:

• Owner: @ggrg
• QA/Review: @ggrg

[ggrg]

The following has been confirmed with @MichaelJBRichards: