feat: Add USDC support

[MilGard91]

Context

Issue: #83

Changes proposed in this pull request

• Add USDC as a asset to the store
• Add caching overwrite for constants
• remove comments regarding support for the decimals, because PriceFeedOracle returns rates in asset units
• add asset object to /quote, /capacity and /capacity/{productId} responses
• update openapi docs

/quote

{
  "quote": {
    "totalCoverAmountInAsset": "string",
    "annualPrice": "string",
    "premiumInNXM": "string",
    "premiumInAsset": "string",
    "poolAllocationRequests": [
      {
        "poolId": "string",
        "coverAmountInAsset": "string",
        "skip": false
      }
    ],
    "asset": { // <--- new asset field
      "id": "string",
      "symbol": "string",
      "decimals": 18
    }
  },
  "capacities": [
    {
      "poolId": "string",
      "capacity": [
        {
          "assetId": "string",
          "amount": "string",
          "asset": { // <--- new asset field
            "id": "string",
            "symbol": "string",
            "decimals": 18
          }
        }
      ]
    }
  ]
}

/capacity/{productId}

{
  "productId": 0,
  "availableCapacity": [
    {
      "assetId": 0,
      "amount": "string",
      "asset": { // <--- new asset field
        "id": "string",
        "symbol": "string",
        "decimals": 18
      }
    }
  ],
  "allocatedNxm": "string",
  "minAnnualPrice": "string",
  "maxAnnualPrice": "string"
}

/capacity

[
  {
    "productId": 0,
    "availableCapacity": [
      {
        "assetId": 0,
        "amount": "string",
        "asset": { // <--- new asset field
          "id": "string",
          "symbol": "string",
          "decimals": 18
        }
      }
    ],
    "allocatedNxm": "string",
    "minAnnualPrice": "string",
    "maxAnnualPrice": "string"
  }
]

Test plan

• Add tests for USDC support
• Add tests for asset object response

Checklist

• [x] Rebased the base branch
• [x] Attached corresponding Github issue
• [x] Prefixed the name with the type of change (i.e. feat, chore, test)
• [x] Performed a self-review of my own code
• [x] Followed the style guidelines of this project
• [ ] Made corresponding changes to the documentation
• [x] Didn't generate new warnings
• [x] Didn't generate failures on existing tests
• [x] Added tests that prove my fix is effective or that my feature works

Review

When reviewing a PR, please indicate intention in comments using the following emojis:

• :cake: = Nice to have but not essential.
• :bulb: = Suggestion or a comment based on personal opinion
• :hammer: = I believe this should be changed.
• :thinking: = I don’t understand something, do you mind giving me more context?
• :rocket: = Feedback

[rackstar]

looks good. as discussed maybe consider adding decimal info for the asset for the 3rd party integration (oper cover, etc..)

[rackstar]

looks good. as discussed maybe consider adding decimal info for the asset for the 3rd party integration (oper cover, etc..)

Added asset.decimal info

[rackstar]

@MilGard91 FE guys agreed that being consistent is better. so we went with:

{
  "quote": {
    ...
    "asset": { <--- asset object containing all info
      "id": "string",
      "symbol": "string",
      "decimals": 18
    }
  },
  "capacities": [
    {
      "poolId": "string",
      "capacity": [
        {
          ...
          "asset": { <--- asset object containing all info
            "id": "string",
            "symbol": "string",
            "decimals": 18
          }
        }
      ]
    }
  ]
}

[rackstar]

I would also bump the deployments package, everything else LGTM

done