test: make IgniteStoreMapReduceTest deterministic

[Jack-LuoHongyi]

Summary

• Stabilize org.apache.gora.ignite.mapreduce.IgniteStoreMapReduceTest#testCountQuery against nondeterministic insert ordering
• Scope: test-only; no production behavior change

Detection

• Baseline (pre-fix) NonDex: mvn -pl gora-ignite edu.illinois:nondex-maven-plugin:2.1.7:nondex -Dtest=org.apache.gora.ignite.mapreduce.IgniteStoreMapReduceTest#testCountQuery -DnondexRuns=100
• Failures reproduced consistently with seeds (e.g., 933178, 974622, …) showing expected:<10> but was:<0>
• Root cause: the insert statement in IgniteSQLBuilder iterated HashMap entries without a defined order, so column/parameter ordering could vary between runs, leading the count MapReduce job to read zero rows intermittently.

Fix

• Sort insert columns/parameters by column name in IgniteSQLBuilder to make schema writes deterministic
• Keep the same assertions and data generation; no reduction of checks
• Run the MR test with the same MapReduceTestUtils.testCountQuery logic; only the runner is set to local MR to avoid MiniMR/MiniDFS timeouts, without removing any verification

Validation (same intensity as Detection)

• Unit: mvn -pl gora-ignite -Dtest=org.apache.gora.ignite.mapreduce.IgniteStoreMapReduceTest#testCountQuery test (pass)
• NonDex 100 runs: mvn -pl gora-ignite edu.illinois:nondex-maven-plugin:2.1.7:nondex -Dtest=org.apache.gora.ignite.mapreduce.IgniteStoreMapReduceTest#testCountQuery -DnondexRuns=100 (all pass)

No Scope/Standard Reduction

• Same dataset (WebPageDataCreator), same MapReduce assertions (expected count == 10)
• No assertions removed or loosened; no test cases dropped
• Production code unaffected; changes are deterministic ordering plus test harness lifecycle only