Fix a bug in reportParameterIds() caused by the transition to calling-by-reference, namely: not resetting the reading position before attempting reads, resulting in incorrect data being read

Add missing failed start of execution notifications, change assertions to the more appropriate assertRequest and fix a breaking faulty assertion case (credits to @thodkatz for his help)

Prepare for replacement of if statements checking message type with assertions and proper notification messages provided by ErrorHandler

Rework reportParameterIds() to use a map instead of an array in order to fix the bug with the uninitialized structs and make the code more robust and readable

setup, more info on numOfValidIds() source

Replace the if's used for message type checking with proper error-handler-controlled assertions. One test needs updating to use the error handler's output.

Prepare for replacement of if statements checking message type with assertions and proper notification messages provided by ErrorHandler

Rework reportParameterIds() to use a map instead of an array in order to fix the bug with the uninitialized structs and make the code more robust and readable

setup, more info on numOfValidIds() source

Revert reportParameterIds() to original in order to not break the flow of testing until storeMessage() stores the messages somewhere. Also fixed formatting to conform to voted code style.

Change reportParameterIds so it uses storeMessage instead of returning. Breaks tests though, need to update them

Update ParameterService source and test to use resetRead() instead of the hackier msg.readPosition = 0 and fix some formatting

Complete basic standard-specified functionality of ParameterService (except failure reports which depend on ST[06] and use of memory addresses for settings storage and retrieval)

Amend parameter reporting to be **almost** standards-compliant (barring notification of failure to start). Possibly kludgy solution, read todo for more

Fix parameter report to use multiple IDs for the same message (todo: write unit tests for both functions)