Inconsistent use of JSON keys snake_case and camelCase in responses

[ivarprudnikov]

Inconsistent use of JSON keys: snake_case vs camelCase

Configuration object is using snake_case and is exposed to the user. The /entries/txIds endpoint returns a list that has nextLink, see renaming logic in JSON

scitt-ccf-ledger/app/src/call_types.h

Lines 75 to 78 in 5cea879

	DECLARE_JSON_REQUIRED_FIELDS_WITH_RENAMES(
	GetEntriesTransactionIds::Out, transaction_ids, "transactionIds");
	DECLARE_JSON_OPTIONAL_FIELDS_WITH_RENAMES(
	GetEntriesTransactionIds::Out, next_link, "nextLink");

Expected behavior
All JSON keys should use camelCase naming convention.

[achamayou]

This is consistent with the current state of the spec: https://github.com/ietf-wg-scitt/draft-ietf-scitt-scrapi/blob/main/draft-ietf-scitt-scrapi.md#transparency-configuration, although the layout of the config object has changed and moved to CBOR since.