Refactor Collection instantiations to use factory methods

[Copilot]

Standardize Collection creation across the codebase to use factory methods from microsphere-collection utilities, improving code consistency and maintainability. This aligns with established patterns and enables better encapsulation of collection initialization logic.

Changes

• ListUtils factory methods: Replaced new ArrayList<>() and new LinkedList<>() with newArrayList() and newLinkedList()
• MapUtils factory methods: Replaced new HashMap<>() with newHashMap()
• SetUtils factory methods: Replaced new ConcurrentSkipListSet<>() with newConcurrentSkipListSet()
• Import statements: Added specific static imports for each factory method (no wildcard imports)

Example

// Before
List<ObjectInstance> instances = new LinkedList<>();
Map<String, Layout> delegatingLayouts = new HashMap<>();
List<Extension> extensions = new ArrayList<>(this.isClassTemplate ? 2 : 1);

// After
import static io.microsphere.collection.ListUtils.newLinkedList;
import static io.microsphere.collection.MapUtils.newHashMap;
import static io.microsphere.collection.ListUtils.newArrayList;

List<ObjectInstance> instances = newLinkedList();
Map<String, Layout> delegatingLayouts = newHashMap();
List<Extension> extensions = newArrayList(this.isClassTemplate ? 2 : 1);

Scope

• 6 Java files refactored (4 source files, 2 test files)
• No logic changes or JavaDoc modifications
• All collection instantiations in the modified scope replaced with their factory method equivalents

[augmentcode]

🤖 Augment PR Summary

Summary: This PR standardizes collection creation to use Microsphere collection utility factory methods.

Changes:

• Replaced direct instantiations of ArrayList, LinkedList, HashMap, and ConcurrentSkipListSet with ListUtils/MapUtils/SetUtils factory methods
• Added explicit static imports for the selected factory methods across main and test code

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 1 suggestion posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

SmartFileAppenderLayout#selectAppender(...) previously relied on new HashMap<>(logger.getAppenders()) to always create a defensive copy before remove(NAME). Can you confirm MapUtils.newHashMap(map) also always returns a new mutable copy (never the same instance or a view), otherwise this would mutate the logger's original appender map?

Severity: medium

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}