Add sled policy data to sled page

[charliepark]

This PR adds policy data (already present on the sleds overview page) to the individual sled view page.

Before:

After:

This does lose the Location | Coming soon line, but I suspect that was added as a means of balancing the rows.
It also adjusts the order of cells in a way that makes more sense on a larger window (like having the two "Usable _____" cells in the bottom of the right-hand column), but as most of our layouts are optimized for desktops over mobile, this seemed like it made more sense.

Closes #2837

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
console	✅ Ready (Inspect)	Visit Preview	Jul 2, 2025 9:48pm

[david-crespo]

We have this second layer of header in the list view to explain what "kind" means and to group kind and provision policy like they are in the response. (Though to be honest it's still not particularly intuitive.) We can't quite do that here, but calling kind "policy kind" might help. On the other hand it might look weird to have "policy kind" and "provision policy". Maybe @benjaminleonard will have an idea.

console/app/api/__generated__/Api.ts

Lines 3632 to 3644 in e71c828

	export type SledPolicy =
	/** The operator has indicated that the sled is in-service. */
	| {
	kind: 'in_service'
	/** Determines whether new resources can be provisioned onto the sled. */
	provisionPolicy: SledProvisionPolicy
	}
	/** The operator has indicated that the sled has been permanently removed from service.
	This is a terminal state: once a particular sled ID is expunged, it will never return to service. (The actual hardware may be reused, but it will be treated as a brand-new sled.)
	An expunged sled is always non-provisionable. */
	| { kind: 'expunged' }

[charliepark]

Chatted with Ben on it and he 👍'd POLICY KIND:

[david-crespo]

Looks good!

It seems like the elimination of PropertiesTable.Group in #2723 means we have an ordering problem. We might be able to fix this by changing the component so it goes by column instead of by row? Making a separate issue for this.