Modify the data models for User Status

The current datamodel for User Status is as follows

{
  "id": "String",
  "userId": "String",
  "currentStatus": {
    "state": "OOO | IDLE | ACTIVE",
    "updatedAt": "TimeStamp",
    "from": "TimeStamp",
    "until": "TimeStamp",
    "message": "String"
  },
  "futureStatus": {
    "state": "OOO | IDLE | ACTIVE",
    "updatedAt": "TimeStamp",
    "from": "TimeStamp",
    "until": "TimeStamp",
    "message": "String"
  },
  "monthlyHours": {
    "committed": "Number",
    "updatedAt": "TimeStamp"
  }
}

According to @ankushdharkar's comments here, we should change this as follows.

{
  "id": "String",
  "userId": "String",
  "status": {
    "current": {
      "state": "OOO | IDLE | ACTIVE",
      "updatedAt": "TimeStamp",
      "from": "TimeStamp",
      "until": "TimeStamp",
      "message": "String"
    },
    "future": {
      "state": "OOO | IDLE | ACTIVE",
      "updatedAt": "TimeStamp",
      "from": "TimeStamp",
      "until": "TimeStamp",
      "message": "String"
    }
  },
  "monthlyHours": {
    "committed": "Number",
    "updatedAt": "TimeStamp"
  }
}

Start by locating the User Status data model and its usages in the backend, then compare them with the proposed nested status structure in the issue. Done means the model and affected references consistently use status.current and status.future while preserving monthlyHours.