SinkBinding does not clear NoAddressable

**Describe the bug**
When we create a `ContainerSource` before creating it's corresponding sink, the `SinkBinding` correctly goes to `NoAddressable`; however, this frequently fails to clear when the sink becomes available, and does not get resolved within a reasonable time limit (we have monitored for 10m before manually intervening).

Restarting the `eventing-webhook` pod immediately resolves the `SinkBinding` status, which in turn is reflected on the `ContainerSource`.

**Expected behavior**
The `NoAddressable` status on the `SinkBinding` (and `ContainerSource`) should clear once the addressable becomes available.

**To Reproduce**
Install a `ContainerSource` with a missing sink. Create the sink. Sometimes the status of the `ContainerSource` and `SinkBinding` will update; sometimes it will not.

**Knative release version**
Operator 1.22.3

Start by reproducing the missing-sink scenario and inspect the SinkBinding and ContainerSource status update path, including logs from the eventing-webhook pod. Confirm the behavior when the sink is created and identify why NoAddressable is not cleared. Done means both resources reliably resolve without restarting eventing-webhook.

Written by the indexing model from the issue text.