[Matter 1.5 TE#2] TC-JFDS-2.1 No evidence logging.

Please follow the below template to file issues/concerns/feature enhancement against Test Scripts:

Summary Title:

TC-JFDS-2.1 provides no evidence of the values read.

Description:

TC-JFDS issues 4 reads for attributes in the test case. The logging shows that a read request was issued and a data report was received. Verbose logging is missing.

Steps to reproduce:

N/A

Logs:

Example of logging level drawn from step 2:
09-23 15:17:50.060 INFO ***** Test Step 2 : TH reads AnchorNodeID attribute from DUT
09-23 15:17:50.061 INFO Found an existing secure session to [8:0000000000000001]!
09-23 15:17:50.062 INFO 0 data version filters provided, 0 not relevant, 0 encoded, 0 skipped due to lack of space
09-23 15:17:50.062 INFO <<< [E:36688i S:2936 M:182630976] (S) Msg TX from 0000000000000065 to 8:0000000000000001 [BFA1] [UDP:[fe80::250:56ff:fe90:fc7d%ens192]:5761] --- Type 0001:02 (IM:ReadRequest) (B:52)
09-23 15:17:50.062 INFO ??1 [E:36688i S:2936 M:182630976] (S) Msg Retransmission to 8:0000000000000001 scheduled for 349ms from now [State:Active II:500 AI:300 AT:4000]
09-23 15:17:50.063 INFO >>> [E:36688i S:2936 M:116650986 (Ack:182630976)] (S) Msg RX from 8:0000000000000001 [BFA1] to 0000000000000065 --- Type 0001:05 (IM:ReportData) (B:71)

Additional Info:

Matter 1.5 TE#2

Search the repository for the TC-JFDS-2.1 test script and inspect how its four attribute reads are logged. Confirm the existing output around the ReadRequest and ReportData messages, then verify that the values read are included as evidence for each attribute.