feat!: Add traits for iterable and non-iterable queries

[DCNick3]

Description

This PR is a first step towards more type-safe queries (#4569). It adds traits for singular and iterable queries and prohibits supplying filters, sorting, pagination and batching parameters in compile time (it is already a runtime error to do so).

Linked issue

Partially addresses #4569

Benefits

• less error prone API
• lays foundation to allow type-checking query filters

Checklist

• make CI pass

[0x009922]

LGTM.

I noticed that smart_contract and client duplicate impls of query execution, and both have type logic to guard against incorrect use of queries. But this compile-time guard is tested only for client. Would it make sense to make a ui test for smartcontracts as well?

Also, do I understand correctly that the runtime check you are talking about is this code?

iroha/core/src/smartcontracts/isi/query.rs

Lines 52 to 63 in 09995af

	// nothing applies to the singular results
	LazyQueryOutput::QueryOutput(output) => {
	if filter != &PredicateBox::default()
	|| sorting != &Sorting::default()
	|| pagination != Pagination::default()
	|| fetch_size != FetchSize::default()
	{
	return Err(Error::InvalidSingularParameters);
	}
	Ok(ProcessedQueryOutput::Single(output))
	}

[DCNick3]

I noticed that smart_contract and client duplicate impls of query execution, and both have type logic to guard against incorrect use of queries. But this compile-time guard is tested only for client. Would it make sense to make a ui test for smartcontracts as well?

I thought about that too, though I just got lazy doing that 😅. I guess I'll update the PR to add that

Also, do I understand correctly that the runtime check you are talking about is this code?

Yes, this is the check I added in #4544 as per your suggestion =)

[Erigara]

Other than comments LGTM