…tion option is true

Signed-off-by: Troy Connor <troy0820@users.noreply.github.com>

…r-election

[release-0.16] 🐛 Add corev1, coordinationv1 scheme for leader election when LeaderElection manager option is true

Signed-off-by: Troy Connor <troy0820@users.noreply.github.com>

…2464-to-release-0.16

[release-0.16] 🐛 Use http client from leaderElectionConfig

* Default namespace only for namespaced object

* Add test

---------

Co-authored-by: Sonu Kumar Singh <sksgkpvks@gmail.com>

Signed-off-by: Troy Connor <troy0820@users.noreply.github.com>

…).Update()

…pdating

Signed-off-by: Troy Connor <troy0820@users.noreply.github.com>

Signed-off-by: Troy Connor <troy0820@users.noreply.github.com>

…2479-to-release-0.16

[release-0.16] 🐛 Do not update anything but status when using subresource client

Before this, Update and Patch requests will override to-level status
fields for objects that have a status resource if the status was
initially empty.

This happens because the code to set the status to what we already have
in the unupdated object converts the object into a `map[string]any`
using json serialization/deserialization, copies the original `status`
field, then converts back. The json deserializer unfortunatelly does not
properly clear the target, allowing data to remain that is absent in the
json serialization.

…2484-to-release-0.16

[release-0.16] 🐛 Fix status subresource getting updated on Update when it is empty

* Draft: Test that an object is updatable after updating its status.

* Draft: ensure we udpate the new obj's accessor's ResourceVersion after doing the deep copy

* Rework code to pass object back on status update

---------

Co-authored-by: Adam Berlin <aberlin@vmware.com>
Co-authored-by: Alvaro Aleman <alvaroaleman@users.noreply.github.com>

…tibility.

…2472-to-release-0.16

[release-0.16] 🐛 Return NoResourceMatchError when appropriate for backwards compatibility.