Ability to provide different block-node-sources.json for each CN that is created

[AlfredoG87]

Requested Feature

Currently when we deploy a Hiero Network using Solo, when using the block node add functionality, it creates its BNs and auto-configures all CNs to stream to all of these BNs.

However there are many instances where we need custom topologies, and even to use an external BlockNode (external of the solo cluster), for that we currently have a workaround that consists in:

1. Create .properties files
2. Create a custom block-node.json source file
3. kill java process within the POD(s)
4. copy files inside the pod
5. copy script to start CN from genesis
6. exec script and use it to start the CN within the POD
7. verify

Business Need

For testing purposes we need to be able to test out different custom network topologies, and also to target an externally deployed BN.

Additional Context

Adding the scripts that I've used to achive a similar outcome in the past manually, after normally deploying with solo.

startPodJava.sh
Taskfile.yaml

Ideally we should be able to define the Hiero network Topology using a single file:

see this example: hiero-ledger/hiero-block-node#1834

[jeromy-cannon]

reopening until solo pr merges