[E2E][JF] Restrict controller apps to scan and pair only with JF-compatible devices.

[vijs]

[vijs]

Moving the conversation from the PR #38994 to here.

Vijay:
Without _J, it's possible that the controller could initiate the Joint Commissioning flow on a device that doesn't support Joint Commissioning, since only service subtypes are filtered according to the current CHIP tool implementation.

Robert:
Upon further research by Doru and I, we believe that the following spec text should be amended in section 4.3.1.7 as follows:

5. The key/value pair CM=3 SHALL indicate that the publisher is currently in Commissioning Mode
   and requires use of a dynamically generated Passcode for commissioning corresponding to the
   verifier that was passed to the device using the OpenJointCommissioningWindow command.

@vijs Please confirm above, I will update the spec text accordingly.