Modify server status endpoints to take Topology parentage into account

[zrhoffman]

I'm submitting a ...

• bug report
• new feature / enhancement request
• improvement request (usability, performance, tech debt, etc.)
• other

Traffic Control components affected ...

• CDN in a Box
• Documentation
• Grove
• Traffic Control Client
• Traffic Monitor
• Traffic Ops
• Traffic Ops ORT
• Traffic Portal
• Traffic Router
• Traffic Stats
• Traffic Vault
• unknown

Expected / new behavior:

Updates should be queued for all of a server's children when updating the status of the server via the following endpoint:

PUT /api/x/servers/:id/status

Current behavior:

Currently, it only queues updates on child caches via the cachegroup's parent_cachegroup and secondary_parent_cachegroup, but it will also need to queue updates on all of the server's children via any Topologies the server's cachegroup is used in also.

Anything else:

Additionally, the following endpoint will need to be updated to take parentage via Topologies into account:

GET /api/x/servers/:host_name/update_status

Currently, it returns parent_pending and parent_reval_pending but only takes into account parents via the server's cachegroup.parent_cachegroup and secondary_parent_cachegroup. It will need to be modified to also take into account parentage via any Topologies the server's cachegroup is used in.