Android add discover

[joonhaengHeo]

Problem

What is being fixed?

• Android Test Application is not supported dns discover. (Python chip-ctrl-tool command is "discover -all")

Change overview

• Add NsdManagerDiscoverService class.
• Support discover function in AddressCommissioning activiry.

Testing

How was this tested? (at least one bullet point required)

• Check to be able to discover in Android App.

[CLAassistant]

All committers have signed the CLA.

[Damian-Nordic]

Would it make sense to implement the discovery as part of the existing NsdManagerServiceResolver class and ServiceResolver interface? That would be more aligned with other platforms which always perform the DNS-SD using the common native code.

[austinh0]

Similar to what Damian said - if you are going to add NsdManagerServiceDiscover in the platform code, then you should also implement the platform DnssdImpl::ChipDnssdBrowse.

I can accept doing mDNS discovery purely in the app code (i.e. use NsdManager directly in the app), at least as a temporary solution, but we should not mix these two approaches.

Will review the PR in more detail after this is resolved.

[joonhaengHeo]

@Damian-Nordic In the case of Android, the only way was to call ServiceResolver to know detailed information such as IP Address and discriminator. (I couldn't find another way.)
Also, it was confirmed that if it is called again before the callback of "NsdManager.resolveService", it will surely fail. Therefore, I thought that reusing the existing code would be helpful in solving complex cases in the future.

[joonhaengHeo]

@austinh0 Does it mean that it should be implemented in a jni format similar to the implementation of Service Resolver?

[austinh0]

Looks good overall.

Is there a reason we call discoverCommissionableNodes, wait, and the check getDiscoveredDevice instead of having some sort of callback method that is invoked when a device is discovered? I haven't looked at the native implementation in a while.

[todo]

(#7985): Annotate csrNonce as Nullable.

connectedhomeip/src/controller/java/src/chip/devicecontroller/ChipDeviceController.java

Lines 56 to 66 in 4dad4bb

	* TODO(#7985): Annotate csrNonce as Nullable.
	*
	* @param bleServer the BluetoothGatt representing the BLE connection to the
	* device
	* @param connId the BluetoothGatt Id representing the BLE connection to
	* the device
	* @param deviceId the node ID to assign to the device
	* @param setupPincode the pincode for the device
	* @param csrNonce the 32-byte CSR nonce to use, or null if we want to use
	* an internally randomly generated CSR nonce.
	*/

---

This comment was generated by todo based on a TODO comment in 4dad4bb in #10682. cc @joonhaengHeo.

[todo]

(#8443): This method could benefit from a ChipDevice abstraction to hide

connectedhomeip/src/controller/java/src/chip/devicecontroller/ChipDeviceController.java

Lines 101 to 105 in 4dad4bb

	* TODO(#8443): This method could benefit from a ChipDevice abstraction to hide
	* the pointer passing.
	*/
	public void getConnectedDevicePointer(long nodeId, GetConnectedDeviceCallback callback) {
	GetConnectedDeviceCallbackJni jniCallback = new GetConnectedDeviceCallbackJni(callback);

---

This comment was generated by todo based on a TODO comment in 4dad4bb in #10682. cc @joonhaengHeo.

[todo]

Find out if DNS-SD results for Android should contain interface ID

connectedhomeip/src/platform/android/java/chip/platform/NsdManagerServiceResolver.java

Lines 87 to 97 in 4dad4bb

	// TODO: Find out if DNS-SD results for Android should contain interface ID
	chipMdnsCallback.handleServiceResolve(instanceName, serviceType, serviceInfo.getHost().getHostName(),
	serviceInfo.getHost().getHostAddress(), serviceInfo.getPort(), serviceInfo.getAttributes(), callbackHandle,
	contextHandle);
	if (multicastLock.isHeld()) {
	multicastLock.release();
	}
	mainThreadHandler.removeCallbacks(timeoutRunnable);
	}
	});

---

This comment was generated by todo based on a TODO comment in 4dad4bb in #10682. cc @joonhaengHeo.

[andy31415]

/rebase