fix(test): disable encoded response/request check when map contains multiple elements

[faillefer]

Fix #2012
Disable encoded response/request check when map contains multiple elements. In that situation the encoded/request response varies because of unpredictable map traversal order

[dnwe]

Thanks for looking at this. The change here does fix the test, although if we do want the result to always be reproducible you'd want to sort the parent topic names as well as that is also a map isn't it?

However, it does also raise the question of: "do we want to be sorting/ordering the protocol responses to make testing easier, when the clients themselves don't care?" — I wonder if we should change our comparison method in our tests

[faillefer]

Since iteration order on map is randomized the encoded response is variable and cannot be checked against a fixed byte array.
Should we disable this check as in offset_commit_response_test.go ?

[faillefer]

If we do as in offset_commit_response_test.go the result would be :

faillefer@d3b16f1

[dnwe]

@faillefer yeah I think that’s the best option for now

[faillefer]

@dnwe i've updated the branch associated to this merge request.
Check of encoded response (or request) is not performed when it contains map with multiple elements
(The sort on partition is removed)
I've updated the title and description of the MR