feat: CON-1677 Add user attributes to query calls

[eichhorl]

Interface spec PR: dfinity/portal#6202

Similar to the previous PR adding user attributes to update calls #9582, this PR does the same for query calls. Both message types make use of the same validation function, which currently rejects messages containing any sender info:

ic/rs/validator/src/ingress_validation.rs

Lines 429 to 437 in 1e55617

	fn validate_sender_info<C: HttpRequestContent>(
	request: &HttpRequest<C>,
	) -> Result<(), RequestValidationError> {
	if request.sender_info().is_some() {
	Err(SenderInfoUnsupported)
	} else {
	Ok(())
	}
	}

Therefore, as with update calls, any query containing a sender_info field set to Some(_) value is still rejected for now.

Note that currently, the new sender_info field doesn't affect the query cache. Assuming setting sender_info were allowed, this means that sending the same query a second time, but with different sender_info, would lead to a cache hit. This should likely be changed in a follow-up.

[mraszyk]

Note that currently, the new sender_info field doesn't affect the query cache.

Could you please create a jira ticket so that this information is not lost?

[eichhorl]

Note that currently, the new sender_info field doesn't affect the query cache.

Could you please create a jira ticket so that this information is not lost?

I saw there is already a ticket here: https://dfinity.atlassian.net/browse/DSM-119