FISH-8334 Fix Incorrect Hazelcast Config for Instances in Deployment Groups

[Pandrex247]

Description

Fixes instances in a deployment group getting the incorrect configuration getting injected.

Important Info

Blockers

None

Testing

New tests

None

Testing Performed

• Disable auto increment port: Admin Console > Domain > Data Grid > Auto Increment Port > Disable
• Create an instance: instance1
• Create a second instance: instance2
• Set Hazelcast port for instance1 to 12000
• Set Hazelcast port for instance2 to 13000
• Restart DAS
• Create a deployment group and add instance1 & instance2 to it: group1
• Start deployment group: both instances should start successfully, with instance1 binding Hazelcast to 12000 and instance2 to 13000 (should be no port conflicts, as this would imply both instances are using the same Hazelcast config and trying to bind to the same port)

Testing Environment

Windows 11, Zulu 11.0.23

Documentation

N/A

Notes for Reviewers

None

[breakponchito]

I already tested and the results were as expected