feat(sdf): Add apply/merge_status automation API endpoints

[jkeiser]

• Copies over almost verbatim the existing force_apply and request_approval endpoints to the automation API, so that we can make a Github Action trigger a management function and merge to HEAD (or request merge to head).
• Adds a "merge_status" endpoint to the automation API, which yields the status of the changeset and any actions enqueued from it in this format:

  {
    "changeSet": {
      "createdAt": "2025-01-18T01:20:59.869049Z",
      "updatedAt": "2025-01-18T01:25:44.315196Z",
      "name": "2025-01-18-01:20",
      "id": "01JHVFZFYS5N65J4QN76004G9N",
      "status": "Applied",
      "baseChangeSetId": "01JH8VFFYD4FAYF1VPCS7TSWHX",
      "workspaceId": "01JH8VEGZYXF5WYFF9Z538F3Q0",
      "mergeRequestedByUserId": "01JH8VEGMN6Q385M3Q44RWJG22",
      "mergeRequestedByUser": "jkeiser",
      "mergeRequestedAt": "2025-01-18T01:25:44.264742Z",
      "reviewedByUserId": "01JH8VEGMN6Q385M3Q44RWJG22",
      "reviewedByUser": "jkeiser",
      "reviewedAt": "2025-01-18T01:25:44.265236Z"
    },
    "actions": [
      {
        "id": "01JHVFZGPZNAH3V455GQZQ73Q0",
        "component": {
          "id": "01JHVFZGPW25N85NJ1SGGVYDRR",
          "name": "foo-vpc"
        },
        "state": "Failed",
        "kind": "Create",
        "name": "Create"
      },
      {
        "id": "01JHVFZGPW25N85NJ1SGGVYDRM",
        "component": {
          "id": "01JHVFZGPSN7RK7T20B1F22S2T",
          "name": "EIP_1"
        },
        "state": "Failed",
        "kind": "Create",
        "name": "Create"
      },
      {
        "id": "01JHVFZGPKPGGMP0T67KHHESE9",
        "component": {
          "id": "01JHVFZGPG2FB6H27VG5JCC3G3",
          "name": "foo-Public Route Table"
        },
        "state": "Queued",
        "kind": "Create",
        "name": "Create"
      },
    ]
  }

Testing

I've tested all three of these endpoints through curl. There are no automated tests in this commit (as with other automation API endpoints), but tests of the github action itself (which are more end to end) will include these. There will be a couple more turns of the crank on these APIs over the next week.

I have verified existing functionality is generally working through the webui as well (creating components, running management functions, and applying changesets). Beyond that, this is entirely new code, limited to the new endpoints under a feature flag, so there should be no risk to the main product.

[github-actions]

Dependency Review

✅ No vulnerabilities or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Files

[jkeiser]

Dropping this back to Draft briefly to add another endpoint. May as well round it out!

[johnrwatson]

@jkeiser Component type would be super useful in this response

{
      "id": "01JHVFZGPW25N85NJ1SGGVYDRM",
      "component": {
        "id": "01JHVFZGPSN7RK7T20B1F22S2T",
              <------- in here!
        "name": "EIP_1"
      },
      "state": "Failed",
      "kind": "Create",
      "name": "Create"
    },
    ```

[jkeiser]

@johnrwatson will do! I want to get this merged soon to unblock, but I'll post a followup with a little more meat on the responses!