Better Visual Hierarchy

About half the table views have "expanded row" displays including additional information. These views can be hard to read. An Outpost has both event-driven Tasks and time-based Schedule. This can result in wild nesting:

An Outpost has:

- Schedules
- A schedule has Tasks
- Tasks have Logs
- Logs have details
- Tasks
- Tasks have Logs
- Logs have details

The display of this information has a poor hierachy. Headers are not used consistently. There is zero visual separation between the Schedules block and the Tasks block.

A similar issue occurs in Blueprints. Blueprints have Schedules as well, but Blueprints also have a Path. Because the Path is not part of the regular metadata displays, it's simply shoved at the top of the Schedule section, a loose bit of information with no contextual meaning or reason for being there.

Task:

Review every expansion row. Where there are multiple containers at any level of expansion, create a better visual hierachy: use header size and a deliberate primary/secondary/tertiary/etc color scheme to help the user better understand what they're looking at.