refactor(uvm): split Update into WCOW and LCOW specific files

[Copilot]

UtilityVM.Update mixed WCOW and LCOW resource handling in a single method, making it harder to maintain and extend independently per container type.

Changes

• update_uvm_wcow.go — new file with updateWCOW, handling *specs.WindowsResources (memory limit, CPU maximum/shares)
• update_uvm_lcow.go — new file with updateLCOW, handling *specs.LinuxResources (memory limit, CPU quota/shares) and *ctrdtaskapi.PolicyFragment
• update_uvm.go — replaced monolithic implementation with a thin OS dispatcher:

func (uvm *UtilityVM) Update(ctx context.Context, data interface{}, annots map[string]string) error {
    if uvm.operatingSystem == "windows" {
        return uvm.updateWCOW(ctx, data, annots)
    }
    return uvm.updateLCOW(ctx, data, annots)
}

This mirrors the existing create_wcow.go/create_lcow.go pattern and makes the separation ready for future compile-time build tag gating if WCOW-only or LCOW-only binaries are needed.

Original prompt

if i need to segregate the Update method into 2 such that WCOW functionality is specific to WCOW file and LCOW in LCOW file. Then we can have same method in both files and can compile the correct file at compile time using build tags. How should I refactor it? Just tell me the approach

The user has attached the following files from their workspace:

• internal/uvm/update_uvm.go

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.