WIP -- create backfill tracker thrift apis (#224)

## Summary

Input/out schema for the Job tracker and lineage API on ZiplineHub. 

## Checklist
- [ ] Added Unit Tests
- [x] Covered by existing CI
- [ ] Integration tested
- [ ] Documentation update


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Introduced a comprehensive job tracking system with support for
tracking job execution, status, and metadata.
	- Added a new API endpoint for handling job type requests.
- Defined structures for job tracking requests and responses, including
job metadata.
- Introduced enumerations for job processing direction, execution modes,
and statuses.
	- Added a new handler for processing job tracking requests.

- **Bug Fixes**
- Corrected a typographical error in a comment within the orchestration
Thrift file.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: ezvz <[email protected]>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

Author: 3 people

api/thrift/hub.thrift

@@ -0,0 +1,117 @@
+namespace py ai.chronon.hub
+namespace java ai.chronon.hub
+
+include "common.thrift"
+include "api.thrift"
+include "orchestration.thrift"
+
+
+/*
+GroupBy APIs
+*/
+
+
+// For an entity-job page, we first call Lineage to get the node graph
+// Then we call JobTrackerRequest on the first level of nodes to render the tasks for the landing page quickly
+// Then we traverse the graph and load the rest of the tasks and statuses
+// If the page was accessed via a "submission" link, then we also render the submission range
+struct LineageRequest {
+    1: optional string name
+    2: optional string type // physical type (limited to backfill or batch upload)
+    3: optional string branch
+    4: optional Direction direction
+
+}
+
+struct LineageResponse {
+    1: optional orchestration.NodeGraph nodeGraph
+    2: optional orchestration.NodeKey mainNode // Same as the node in the LineageRequest
+}
+
+struct JobTrackerRequest {
+   1: optional string name
+   2: optional string type
+   3: optional string branch
+   10: optional DateRange dateRange // We may not need to use this, but in case it helps with page load times
+}
+
+struct JobTrackerResponse {
+   1: optional list<TaskInfo> tasks // Date ranges can overlap for tasks (reruns, retries etc). Need to render latest per day.
+   2: optional orchestration.NodeKey mainNode // Same as the node in the JobTrackerRequest
+}
+
+// Submissions are used to render user's recent jobs on their homepage
+struct SubmissionsRequest {
+    1: optional string user
+}
+
+struct SubmissionsResponse {
+    1: optional list<Submission> submissions
+}
+
+enum Direction {
+   UPSTREAM = 0,
+   DOWNSTREAM = 1,
+   BOTH = 2
+}
+
+struct TaskInfo {
+    1: optional Status status
+    2: optional string logPath
+    3: optional string trackerUrl
+    4: optional TaskArgs taskArgs
+    5: optional DateRange dateRange // specific to batch nodes
+
+    // time information - useful for gantt / waterfall view
+    10: optional i64 submittedTs
+    11: optional i64 startedTs
+    12: optional i64 finishedTs
+
+    20: optional string user
+    21: optional string team
+
+    // utilization information
+    30: optional TaskResources allocatedResources
+    31: optional TaskResources utilizedResources
+}
+
+struct DateRange {
+    1: string startDate
+    2: string endDate
+}
+
+struct TaskArgs {
+  1: optional list<string> argsList
+  2: optional map<string, string> env
+}
+
+struct TaskResources {
+  1: optional i64 vcoreSeconds
+  2: optional i64 megaByteSeconds
+  3: optional i64 cumulativeDiskWriteBytes
+  4: optional i64 cumulativeDiskReadBytes
+ }
+
+
+enum Mode {
+    ADHOC = 0,
+    SCHEDULED = 1
+}
+
+enum Status {
+   WAITING_FOR_UPSTREAM = 0,
+   WAITING_FOR_RESOURCES = 1,
+   QUEUED = 2,
+   RUNNING = 3,
+   SUCCESS = 4,
+   FAILED = 5,
+   UPSTREAM_FAILED = 6,
+   UPSTREAM_MISSING = 7
+}
+
+struct Submission {
+    1: optional orchestration.NodeKey node
+    10: optional i64 submittedTs
+    20: optional i64 finishedTs
+    21: optional DateRange dateRange
+}

api/thrift/orchestration.thrift

@@ -145,7 +145,8 @@ union PhysicalNodeType {
     4: ModelNodeType modelNodeType
     5: TableNodeType tableNodeType
 }
-// ====================== End of phsical node types ======================
+
+// ====================== End of physical node types ======================
 
 /**
 * Multiple logical nodes could share the same physical node