Remove isNearby filter from AppHelper functions

[luizgrp]

WHAT

1. Remove isNearby filter from connectedNodes and connectedAndInstalledNodes functions from AppHelper.

2. Add isNearby property to AppHelperNodeStatus and update samples to display it.

Phone sample

Screen_recording_20240126_165742.mp4

Wear sample

Screen_recording_20240129_110520.mp4

WHY

I think it was being used as a way to filter "connected" nodes, however, this is not correct.
Retrieving reachable nodes from CapabilityClient already returns nodes that are connected.
IsNearby is only filtering by those connected directly to the caller device.

Use case which shows that it was not working as intended:

1. Switch off bluetooth from the phone;
2. Have a paired watch device connected to wifi;
3. Launch datalayer sample on the phone, go the Nodes or Nodes Listener screen;

Expected result: watch device should be listed.
Actual result: watch device is not listed.

Checklist 📋

• Add explicit visibility modifier and explicit return types for public declarations
• Run spotless check
• Run tests
• Update metalava's signature text files

[garanj]

The original intention of using isNearby was to only include those devices that were connected via BT (as that's the only 1-hop transport supported right now?). This was with the assumptions that:

1. The user would be needing their phone and watch with them (so in close proximity) for whatever they were doing
2. Bluetooth was enabled

Maybe (2) doesn't hold? Maybe some people have BT off?

[luizgrp]

@yschimke @garanj added more changes after our discussion - updated the PR description, including video to the samples - please review again when you get a chance