Bump SpotBugs forked-JVM heap for codenameone-maven-plugin

The module's SpotBugs run with `<effort>Max</effort>` intermittently
OOMs on the default 512MB fork heap, with the JVM crashing inside
FindRefComparison / ResourceValueAnalysis when the type-frame dataflow
expands the larger mojo classes. The crash returns Java exit code 1,
which `failOnError=false` does NOT suppress (that flag only swallows
reported findings, not analysis crashes), so the whole reactor build
dies. Observed on master CI (pojo-annotation-frameworks branch run at
2026-05-27 10:40) as well as on this branch's runs.

Setting `<maxHeap>2048</maxHeap>` lifts the fork heap to 2GB, which
absorbs the spikes seen so far.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: shai-almog

maven/codenameone-maven-plugin/pom.xml

@@ -349,6 +349,17 @@
                     <xmlOutput>true</xmlOutput>
                     <xmlOutputDirectory>${project.build.directory}</xmlOutputDirectory>
                     <excludeFilterFile>${project.basedir}/spotbugs-exclude.xml</excludeFilterFile>
+                    <!--
+                    The default 512MB forked-JVM heap intermittently OOMs on
+                    this module under `<effort>Max</effort>`. Observed on
+                    both PR branches and master: FindRefComparison /
+                    ResourceValueAnalysis blow up the type-frame dataflow on
+                    the larger mojo classes here. Bump to 2GB to absorb the
+                    spikes; `failOnError=false` silences findings but does
+                    NOT catch a Java exit code 1 from an OOM crash of the
+                    fork, so without the bump the build dies anyway.
+                    -->
+                    <maxHeap>2048</maxHeap>
                 </configuration>
                 <executions>
                     <execution>