feat: Add tolerations to WorkspaceKind Form

[thaorell]

closes: #1019

Added:

• Custom types
• Refactored WorkspaceKind PodConfig Tables to have expandable rows
• Add Toleration Modal and Table to PodConfig expanded section: The modal will automatically hide Value input if the operator is Exists and only render Toleration seconds field if the effect is NoExecute
• Add tests

Before:

After:

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign paulovmr for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• workspaces/frontend/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[thaorell]

/ok-to-test

[caponetto]

Left a few comments, please check if they make sense.

Only one UI observation (not blocker): The Toleration modal has a state where Toleration Seconds is not shown, for instance:

When the item is added, the column is displayed, though:

This could confuse users about where that comes from. I would rather disable Toleration Seconds with a helper reason than hide it.

[caponetto]

tolerationSettersCache and modalSettersCache are Map<number, ...> refs that grow monotonically; entries are never removed when pod configs are deleted. While functionally correct (the useMemo re-maps fresh indices), the caches accumulate stale closures over time. For a form with frequent add/remove cycles, consider clearing the caches when podConfig.values.length changes, or switching to a useMemo-based approach without manual caching.

[thaorell]

I'm applying a fix to delete stale cache entries in handleDelete, so when a config is deleted, the config's tolerations will be deleted as well

[caponetto]

TolerationOperator.None = '' and TolerationEffect.None = '' use empty strings as enum values. When these are serialized and sent to the backend (or eventually to the Kubernetes API), empty strings may behave differently from an omitted field. Please confirm that the backend handles empty-string operator/effect correctly, or consider using undefined/omission to represent "no selection" and making the field optional in TolerationEntry.

[thaorell]

After reading the Kubernetes docs in depth, I am setting the default Operator to Equal

[thaorell]

I also added a description for a None effect, which will be coerced to undefined upon submission

[caponetto]

The descriptive text block uses raw <div> elements with PatternFly utility classes. Since Content is already imported, prefer <Content component="p"> for the description paragraph. This ensures consistent typography and spacing from PatternFly's design system rather than relying on utility classes alone.

[caponetto]

/lgtm

[caponetto]

/lgtm