Improve NameRes memory and Solr cache configuration

[gaurav]

Summary

• Reduced NameRes heap_mem and removed the minimum memory constraint (Reduce Solr JVM heap to leave room for OS page cache NCATSTranslator/NameResolution#265)
• Enlarged Solr queryResultCache for NameRes, which was badly undersized (~56% hit rate, 317K evictions), now configurable via values.yaml (Grow queryResultCache (size=512, 56% hit rate, 317K evictions) NCATSTranslator/NameResolution#266)
• Cleaned up contradictory Solr G1 GC flags — removed young-generation size pins that were overriding G1's adaptive pause-target logic, and set -Xms == -Xmx to avoid runtime heap resizing (Revisit Solr JVM GC flags: pinned young generation disables the G1 pause-time goal; collect GC logs under load NCATSTranslator/NameResolution#272)
• Increased CPU limit slightly (6 → 7) for NameRes
• Increased memory and CPU for NameRes Dev at RENCI

Test plan

• Verify NameRes Exp at RENCI starts successfully with updated resource limits
• (IMPORTANT) Verify that doing an upgrade with this code of NameRes Dev comes up without any issues -- while some features won't work until we next reload the database, if restarting NameRes causes an issue, then NameRes CI will be down until its database can be upgraded, which would not be ideal!
• Monitor Solr query cache hit rate after deployment to confirm improvement from ~56% baseline
• Confirm no GC-related performance regressions (G1 should now size young gen against 200ms pause target)
• Check that heap does not resize at runtime (Xms == Xmx)

🤖 Generated with Claude Code