Update the chunk capabilities while setting data for a connection

[bharathreddy403]

According to the Capabilities test cases (Section 2.4):
Requester → GET_CAPABILITIES
{ SPDMVersion = NegotiatedVersion, Flags &= ~CHUNK_CAP, DataTransferSize ≠ MaxSPDMmsgSize }
Condition: NegotiatedVersion ≥ 1.2

The CHUNK_CAP flag is not set when configuring the connection. Later, during connection initialization in the test cases, the function libspdm_mask_capability_flags() is invoked, which applies a logical AND (&&) to the capability flags based on the negotiated version and existing flags.
Additionally, during initialization, the values of "data_transfer_size" and "max_spdm_msg_size" are not equal. This mismatch causes the responder to fail consistently, resulting in the test cases being skipped.

Failure:
test assertion 3.2.0 - NOT_TESTED case_setup_func fail
test assertion 3.4.0 - NOT_TESTED case_setup_func fail
test assertion 3.6.0 - NOT_TESTED case_setup_func fail
test assertion 3.7.0 - NOT_TESTED case_setup_func fail
test assertion 4.1.0 - NOT_TESTED case_setup_func fail
test assertion 4.2.0 - NOT_TESTED case_setup_func fail
test assertion 5.1.0 - NOT_TESTED case_setup_func fail
test assertion 5.2.0 - NOT_TESTED case_setup_func fail

@steven-bellock and @jyao1, please check this PR changes.

[steven-bellock]

@bharathreddy403 please file an issue (https://github.com/DMTF/SPDM-Responder-Validator/issues). The sequence of events that lead to this issue are not clear to me.

[bharathreddy403]

@bharathreddy403 please file an issue (https://github.com/DMTF/SPDM-Responder-Validator/issues). The sequence of events that lead to this issue are not clear to me.

Sure I will raise the issue, and explain the series of steps.