Updates to the next links parameter in the read complaint endpoint

Previously, calling the read complaint endpoint when there was an outstanding question to be answered would return a link to the complaint itself as seen in the example below.

{
  "token": "<complaint_token>",
  "interview": "<interview_token>",
  "interpreations": [
    {
      <truncated>
    }
  ],
  "clarifications": [
    {
    	<truncated>
    }
  ],
  "_links": {
    "next": "https://api.buoyhealth.com/symptom-checker/v2/complaints/<complaint_token>
  }
}

Going forward, if there are outstanding questions needed to clarify a complaint, the read complaint endpoint will return a link to the next question to be answered.

{
  "token": "<complaint_token>",
  "interview": "<interview_token>",
  "interpreations": [
    {
      <truncated>
    }
  ],
  "clarifications": [
    {
    	<truncated>
    }
  ],
  "_links": {
    "next": "https://api.buoyhealth.com/symptom-checker/v2/questions/<question_token>
  }
}

This change will allow API clients to successfully read the next question for a complaint in instances where the read complaint endpoint is being called. Previously, next questions were only visible upon receiving the response from the update complaint or update question endpoint.

This change is not expected to be breaking and will replace existing functionality on the v2 endpoints.