fix: update audit table API permissions so unpublished routes can render PlanningConstraints

[jessicamcinchak]

August flagged this morning that on /unpublished routes, PlanningConstraints are failing to render correctly & throwing the following console error:

{
 "extensions": {
    "path": "$.selectionSet.insert_planning_constraints_requests_one",
    "code": "validation-failed"
  },
  "message": "field "insert_planning_constraints_requests_one" not found in type: 'mutation_root'"
}

Before: https://editor.planx.uk/barnet/find-out-if-you-need-planning-permission/unpublished
After: https://2392.planx.pizza/barnet/find-out-if-you-need-planning-permission/unpublished

Changes:

• Update planning_constraints_requests table to grant the api role select permissions, consistent with other audit tables, as this is necessary for the insert_ mutation to return the new record's id
• Adjust frontend conditional rendering so in cases of an error, that's all we ever display - never a mix of error plus successful roads response like happened in this edge case

This bug is only effecting /unpublished routes, not /preview, so no particular rush to deploy

[github-actions]

🤖 Hasura Change Summary compared a subset of table metadata including permissions:

Updated Tables (1)

• public.planning_constraints_requests permissions:

  	insert	select	update	delete
  api		➕

  5 added column permissions

  	insert	select	update
  api		➕ created_at ➕ destination_url ➕ id ➕ response ➕ session_id

[github-actions]

Removed vultr server and associated DNS entries

[DafyddLlyr]

Thanks for picking this one up!