umock_c_get_expected_calls and umock_c_get_actual_calls should return some "collection" of calls

umock_c_get_actual_calls should return some "query-able" collection of calls.

That way, in the scenario of "was function X called?" (notice: the scenario is missing any sort of ordering or __other__ functions being called) there would be some answer.

Right now, the only verification of umock_c is "did all functions match in order?" (by means of ASSERT_ARE_EQUAL(char_ptr, umock_c_get_expected_calls(), umock_c_get_actual_calls()); that actually compares 2 strings).

Having a collection of calls exposed would mean the user can better decide when "my test failed". Sometimes all the user cares is "was this callback called with these parameters?" disregarding any other function calls.

Start by reading the existing umock_c_get_expected_calls and umock_c_get_actual_calls APIs and the ASSERT_ARE_EQUAL(char_ptr, umock_c_get_expected_calls(), umock_c_get_actual_calls()) usage described in the issue. Define and document the collection and query behavior before implementation; done should let users check whether a callback was called with specified parameters without requiring call ordering or excluding other calls.

Written by the indexing model from the issue text.