Used tasks to help out with this one, as I'm not super familiar with the template build and validation process yet.

The changes here introduce a deployment wide minimum agent metadata interval via CLI flag/env var. This is then applied in astrict way to new templates/new builds of existing templates, such that the template build will fail if it has a metadata interval does not comply with the minimum set for the coderd config value. Additionally, workspaces from existing template versions will have their agent metadata intervals "silently" upgraded (we log the upgrade but don't fail the workspace build) to comply with the config value.

This should allow coder deployment admins more control over deamplifying the volume ofUpdateWorkspaceAgentMetadata db calls, and the associatedpg_notify calls that go to the Workspace UI page, which is particularly relevant in larger organizations with high workspace counts/more metadata per agent.

Logging of the upgrade for a workspace using an existing template verison.

The failure message for a new template build that contains an invalid agent metdata interval value.

For the workspace built from an existing template, I also manually verified that the 60s upgraded interval value was being respected by using a timer to track changes in values shown on the UI page.