Contradictory description of supported sinkCredential.credentialType values

[hdamker]

Problem description
The description states the sinkCredential.credentialType constraint twice, with conflicting values:

• L31: "MUST be set to ACCESSTOKEN or PRIVATE_KEY_JWT if provided"
• L93-94: "MUST be set to ACCESSTOKEN if provided"

Expected behavior
Align both statements with the schema enum (ACCESSTOKEN, PRIVATE_KEY_JWT). The two paragraphs are otherwise near-duplicates, so consider removing one instead of maintaining both.

Alternative solution
None

Additional context

PredictiveConnectivityData/code/API_definitions/predictive-connectivity-data.yaml

Line 31 in ecd8a33

property to protect the notification endpoint. In the current version,`sinkCredential.credentialType` MUST be set to `ACCESSTOKEN` or `PRIVATE_KEY_JWT` if provided.

PredictiveConnectivityData/code/API_definitions/predictive-connectivity-data.yaml

Lines 93 to 94 in ecd8a33

	notification endpoint. In the current version, sinkCredential.credentialType
	MUST be set to ACCESSTOKEN if provided. When an asynchronous response is