Many to many parent_id to child_id mapping should rely on coerced values

[JingLi1998]

Currently the query engine is broken for m2m relationships when using bigint as the primary key. Related issue

The culprit seems to be an inconsistent usage of coerced and non-coerced values when inserting and getting values from the id_map variable.

prisma-engines/query-engine/core/src/interpreter/query_interpreters/nested_read.rs

Lines 80 to 89 in 55eef36

	let mut id_map: HashMap<SelectionResult, Vec<SelectionResult>> = HashMap::new();
	for (parent_id, child_id) in ids {
	match id_map.get_mut(&child_id) {
	Some(v) => v.push(parent_id),
	None => {
	id_map.insert(child_id.coerce_values()?, vec![parent_id.coerce_values()?]);
	}
	};
	}

[Weakky]

Hey @JingLi1998,

The original issue was closed a while ago and we just realized you had posted a PR for it. Sorry we didn't see your PR earlier 🙏

Please re-open if you think it's still an issue.

Thanks!