Gate flaky performance-threshold tests behind performRelease

testAtomicTypesPerformance (100ms threshold) and
testSetVsListInsertionPerformance (10x ratio threshold) fail on slower
CI hardware. Gate them with @EnabledIfSystemProperty(performRelease)
like other performance benchmarks so they run during release builds
on known hardware but not on CI.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: jdereg

src/test/java/com/cedarsoftware/util/MultiKeyMapAtomicTypesTest.java

@@ -210,6 +210,7 @@ void testAtomicTypeBasedEqualityWhenDisabled() {
     }
 
     @Test
+    @org.junit.jupiter.api.condition.EnabledIfSystemProperty(named = "performRelease", matches = "true")
     void testAtomicTypesPerformance() {
         MultiKeyMap<String> map = MultiKeyMap.<String>builder().valueBasedEquality(true).build();
 

src/test/java/com/cedarsoftware/util/MultiKeyMapSetPerformanceTest.java

@@ -39,6 +39,7 @@
 class MultiKeyMapSetPerformanceTest {
 
     @Test
+    @org.junit.jupiter.api.condition.EnabledIfSystemProperty(named = "performRelease", matches = "true")
     void testSetVsListInsertionPerformance() {
         MultiKeyMap<String> map = new MultiKeyMap<>();
         int iterations = 10000;