Common scenario test network operation implementation

[bestbeforetoday]

As a maintainer
I want a single component for network operations in scenario tests
So that I don't need to maintain multiple language implementations of the same code

The scenario tests perform both:

1. Common network operations, such as creating the Fabric network and running Docker commands.
2. Interacting with the Fabric network using the language-specific client API.

The common operations are currently reimplemented in each of the scenario test languages (Go, Node, Java). Each of these common operations involves orchestration of multiple CLI commands, which are the same in each scenario test language implementation.

It would be helpful to avoid duplication and maintenance overhead for the common network operations to be implemented in a single component, which in then invoked (perhaps as a simple CLI command) by each scenario test language implementation. A Go implementation of this common behaviour could be based on the current Go scenario test implementation logic, but use Go libraries rather than external CLI commands for many of the operations:

• Docker: https://pkg.go.dev/github.com/docker/docker/client
• Fabric: https://github.com/hyperledger/fabric-admin-sdk