Separating the Vault status in the vault table: accepting issues requests and collateral levels

[nud3l]

Is your feature request related to a problem? Please describe. In the Vault table( e.g., https://kintsugi.interlay.io/dashboard/vaults), we show a "Status" column that mixes collateral levels and the Vault's setting to accept issue requests. However, this does not work well as we have combined states such as (ACCEPT_ISSUE_FALSE && BELOW_SECURE_THRESHOLD).

In the screenshot below, Vault a3fxCi...669v6eN is below the secure threshold but also not accepting new requests.

Describe the solution you'd like

I would like to adjust the table as follows:

1. Collateralization column currently shows the actual collateralization with a color coding.

• Add the worded collateral status as an enum that says one of "Above Secure Threshold", "Above Premium Redeem Threshold", "Above Liquidation Threshold", or "Liquidated"
• Link in the tooltip to the collateralization threshold docs: https://docs.interlay.io/#/vault/overview?id=collateral-thresholds

2. Rename the Status column to Accepting new iBTC and only track if Vaults accept new issue request or not. Possible states: "Active", "Inactive", "Liquidated".

Describe alternatives you've considered If adding the worded version of the collateral thresholds as proposed in point 1 above makes the table cluttered, possibly this can just be added in an extra column

Additional context n/a