[Feature]: Support cloud fleet in-place update for provisioning-controlling fields

[r4victor]

Problem

Support in-place update for cloud fleets when provisioning-controlling fields change: resources, backends, regions, availability_zones, instance_types, spot_policy, max_price.

The intended behavior is:

• persist the updated fleet spec in place
• have fleet consolidation detect existing instances that no longer match the updated spec
• terminate non-matching idle instances

Today fleet consolidation only reconciles nodes.min / nodes.max; it does not check instance compatibility against the current fleet spec.

Solution

Workaround

No response

Would you like to help us implement this feature by sending a PR?

Yes