[Bug] [NetworkCommissioning] Empty results of directed ScanNetworks don't return expected NetworkNotFoundError

[Survensa]

Feature Area

Other

Test Case

TC-CNET-4.4

Reproduction steps

1. Bring up the Device Under Test (DUT) with the all-clusters-app.
2. Pair the DUT using chip-tool through the "ble-wifi" transport.
3. Scan the network to know available networks : ./chip-tool networkcommissioning scan-networks 1 0 --Ssid null --Breadcrumb 1
   Note : Select any one SSID as 1ST_ACCESSPOINT_SSID_hex
4. Scan the selected network : ./chip-tool networkcommissioning scan-networks 1 0 --Ssid hex:<1ST_ACCESSPOINT_SSID_hex> --Breadcrumb 2
5. Turn off the 1ST_ACCESSPOINT_SSID_hex wifi
6. Now scan the selected network to expect the NOT FOUND error

Test Plan Expected outcome :

_Verify that the DUT sends the ScanNetworkResponse command with the NetworkingStatus field set to NetworkNotFound._

Expected outcome:

[1683268296.897526][12131:12134] CHIP:TOO: NetworkConfigResponse: {
[1683268296.897745][12131:12134] CHIP:TOO: networkingStatus: 3
[1683268296.898546][12131:12134] CHIP:TOO: }

Actual outcome:

[1707212325.045487][39892:39895] CHIP:TOO: ScanNetworksResponse: {
[1707212325.045576][39892:39895] CHIP:TOO: networkingStatus: 0
[1707212325.045644][39892:39895] CHIP:TOO: wiFiScanResults: 0 entries
[1707212325.045886][39892:39895] CHIP:TOO: }

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

f63b505

Platform

raspi

Logs:
TC_CNET_4_4(ctrl).txt
TC_CNET_4_4(dut).txt

Test Plan Reference: https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/cluster/network_commissioning.adoc#tc-cnet-4-4-wi-fi-verification-for-scannetworks-command-dut-server