fix(QTDI-2567) prevent CacheMap eviction issue

[thboileau]

Requirements

• Any code change adding any logic MUST be tested through a unit test executed with the default build
• Any API addition MUST be done with a documentation update if relevant

Why this PR is needed?

Component-server maintains two maps with a size limit. The code that should take care of this limit throws an exception when called

What does this PR adds (design/code thoughts)?

It prevents the exception, and a test case is also provided.

[Copilot]

Pull request overview

Fixes a runtime exception in MapCache.evictIfNeeded() when trimming concurrent caches used by component-server resources, and adds unit tests to validate eviction behavior.

Changes:

• Fix eviction logic to remove entries safely via iterator next() + remove(), and treat maxSize <= 0 as “clear cache”.
• Add JUnit 5 parameterized tests covering emptying, trimming, and no-op scenarios for evictIfNeeded().
• Minor comment typo fixes in MapCache.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
component-server-parent/component-server/src/main/java/org/talend/sdk/component/server/lang/MapCache.java	Fixes eviction implementation to avoid iterator misuse exceptions when enforcing max cache size.
component-server-parent/component-server/src/test/java/org/talend/sdk/component/server/lang/MapCacheTest.java	Adds unit tests for eviction behavior (empty, trimmed, unchanged).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ypiel-talend]

Just one simple question.

[ypiel-talend]

LGTM