Make the agent mutate on update as well as create

[RothAndrew]

Description

Make the Zarf Agent mutate objects on update as well as create

Related Issue

Fixes #564

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist before merging

• Tests have been added/updated as necessary (add the needs-tests label)
• Documentation has been updated as necessary (add the needs-docs label)
• An ADR has been written as necessary (add the needs-adr label) [ 1 2 3 ]
• (Optional) Changes have been linted locally with golangci-lint. (NOTE: We haven't turned on lint checks in the pipeline yet so linting may be hard if it shows a lot of lint errors in places that weren't touched by changes. Thus, linting is optional right now.)

[RothAndrew]

I have no idea whether this is the only change that is needed to fix #564. My expertise in the area of mutating webhooks is very limited.

[jeff-mccoy]

It looks like a reasonable change, I debated doing both CREATE/UPDATE but didn't consider how Flux might treat things on update. We'll also need to manage a new zarf agent release for this, but will conflict with a new release for #562. Unfortunately the way we release right now you have to manually trigger a pipeline build and then reference that in zarf.

[jeff-mccoy]

Think we'll also have to double-check that we are maintaining idempotent changes for this as well

[RothAndrew]

Do we need a new version of the agent? This is a change to the kubernetes Yamil manifest in the in it package

[jeff-mccoy]

Yeah sorry just saw that, this should be fine as-is, thanks

[RothAndrew]

Thanks! Are you planning on cutting a release with this change? It would help with my DI2-ME work.

[jeff-mccoy]

Yeah, cutting tonight, will be a patch.