fix: spurious logging when discovering capacity (#8143) #10910

Job	Run time
resolve / resolve	4s
e2e-matrix / e2e-upgrade / suite-upgrade	3h 38m 1s
e2e-matrix / e2e (Consolidation, us-east-2, aws) / suite-Consolidation	1h 43m 1s
e2e-matrix / e2e (Drift, us-east-2, all) / suite-Drift	3h 13m 50s
e2e-matrix / e2e (Interruption, us-east-2, aws) / suite-Interruption	1h 1m 40s
e2e-matrix / e2e (Chaos, us-east-2, upstream) / suite-Chaos	1h 0m 51s
e2e-matrix / e2e (Scheduling, us-east-2, aws) / suite-Scheduling	1h 41m 15s
e2e-matrix / e2e (Storage, us-east-2, aws) / suite-Storage	1h 37m 14s
e2e-matrix / e2e (NodeClaim, us-east-2, all) / suite-NodeClaim	1h 28m 26s
e2e-matrix / e2e (Expiration, us-east-2, upstream) / suite-Expiration	51m 10s
e2e-matrix / e2e (Termination, us-east-2, upstream) / suite-Termination	59m 4s
e2e-matrix / e2e (IPv6, us-east-2, aws) / suite-IPv6	50m 48s
e2e-matrix / e2e (LocalZone, us-west-2, aws) / suite-LocalZone	53m 10s
e2e-matrix / e2e (AMI, us-east-2, aws) / suite-AMI	1h 32m 36s
e2e-matrix / e2e (Integration, us-east-2, all) / suite-Integration	3h 54m 44s
	1d 0h 25m 54s

Provide feedback