Consider Topologies parentage when queueing or checking server updates

[zrhoffman]

What does this PR (Pull Request) do?

• This PR fixes Modify server status endpoints to take Topology parentage into account #4847 by adding Topologies support on the following endpoints:
  • PUT /api/3.0/servers/{id}/status
  • GET /api/3.0/servers/{host_name}/update_status

Which Traffic Control components are affected by this PR?

• Documentation
• Traffic Control Client - Go
• Traffic Ops

What is the best way to verify this PR?

Run the API tests

docker-compose -f docker-compose.yml up --build --force-recreate -d
docker-compose -f docker-compose.yml -f docker-compose.traffic-ops-test.yml up --build --force-recreate integration

The following criteria are ALL met by this PR

• This PR includes tests
• This PR includes documentation
• This PR includes an update to CHANGELOG.md
• This PR includes any and all required license headers
• This PR does not include a database migration
• This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

[rob05c]

Looks good! Code generally looks good, mostly minor things. I'm only requesting changes for the log.Error panics, and if you could answer the questions about EDGE? (It might be ok, I'm just not sure, I'll take your word for it)

Haven't run it yet, I'll try to do that shortly

[zrhoffman]

retest this please

[rob05c]

Looks great! Code looks good, unit tests pass, TO API tests pass. Manually tested, setting status on a mid queues edges in its topology, /update_status returns parent_pending when a parent in the topology is queued even if no traditional parents are.

[rob05c]

retest this please