Edge 373 placement controller log decision trace in json

[ktatarnikovhiro]

This PR introduces detailed tracing and logging for placement decisions, propagating structured trace data through models, business logic, and outwards to external consumers. The goal is to retain a fully traceable chain of decision steps for each scheduling/placement operation, improving debugging, auditability, and visibility of how placement outcomes are determined.

Notable Changes

• New Models and OpenAPI Additions:
  • Added TraceLogRowModel and NamespacedNameModel to both Python and OpenAPI schemas.
  • Added trace fields to BidResponseModel and required name in BidRequestModel.
• Trace Propagation:
  • Placement-related objects (GreedyPlacement, PlacementResult, etc.) now accept and record detailed trace logs (TraceLog).
  • Traces are collected as lists of structured TraceLogRow objects, capturing timestamp, zone, application name, message, and state.
• API and Internal Model Updates:
  • Updated API, client, and domain models to support structured traces and propagate them between scheduler, placement, and storage layers.
  • Refactored code to ensure trace information flows through actions, results, and is saved in persistent stores (DecisionStore).
• Test and Fixture Updates:
  • All affected tests now use new trace fields and models, updating expectations and test data for the new format.
• Dependency and Tooling Bumps:
  • Updated core dependencies such as kubernetes, fastapi, uvicorn, and dev tools.
  • Added and pinned certain transitive dependencies for security and compatibility (filelock, urllib3).
• Implementation Details:
  • Added now_millis to clocks to support accurate timestamping of trace log events.
  • Enhanced and formalized logging at scheduling, placement, and result-reporting steps.
  • Adjusted various function/method signatures to accept/return traces as needed.
  • Improved trace resets and composition to enable concatenation of local and remote traces.

Impact

• Debuggability: Each placement attempt now produces a complete, structured trace, making it much easier to follow the decision-making process.
• Auditability: System actions are now tracked with zone, name, time, state, and arbitrary messages.
• Test Coverage: All affected tests have been updated to expect and assert on new trace fields.