CoderMCPServer: status-based ENABLED column and observedGeneration only with fresh conditions #415

Two CoderMCPServer gaps that #408 fixed for CoderAIProvider (#321). Neither blocked #408, which covers only AI providers.

1. The ENABLED column prints spec.enabled. A refused object, or one whose config Coder no longer has, still shows ENABLED true. 🤖 fix: finish the CoderAIProvider activation follow-ups #408 moved the CoderAIProvider column to a status field that holds Coder's last reported value. Do the same for CoderMCPServer.
2. A status write can advance observedGeneration without fresh conditions. In CoderAIProvider, a status write before the PATCH moved status.observedGeneration forward while the conditions still described the old generation. When the PATCH hung, GitOps health rules read the object as healthy. CoderMCPServer saves its config ID after a create with a separate status write before the final status. Check whether that write, or any other intermediate write, can leave observedGeneration ahead of the conditions, and add the regression test that 🤖 fix: finish the CoderAIProvider activation follow-ups #408 added for providers.

Refs #321, #408, #155

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high