Fabric Ops Console: implement `deployer` package

[amozghovyi]

Is your feature request related to a problem? Please describe.

I deployed Fabric v2.5.4 network via Bevel v1.0.1 and Ops Console unable to connect ordering service. Because of this, adding a channel via Ops Console also does not work.

The same issue is in hyperledger-labs/fabric-operations-console#594
In the Dev tools in browser i see the following error while Ops Console trying to connect to Ordering services:

RestApi:GET /deployer/api/v3/instance/$iid/type/orderer/component/gtchkd10ord2 Formatted RestApi error into: REQUEST_ERROR_IN_RESPONSE: GET /deployer/api/v3/instance/$iid/type/orderer/component/gtchkd10ord2 failed with 400:  

details": "this api is not available to Console's without the \"deployer\" counterpart.

The same problem occurred when I tried to use fabric-operations-console docker image (ghcr.io/hyperledger-labs/fabric-console:v1.0.9-5) instead of Bevel Ops Console docker image.:

stitch-dependencies.min.js:72 RestApi: GET /deployer/api/v3/instance/$iid response: {
    "statusCode": 503,
    "error": "api is not available",
    "msg": "this api is not available to Console's without the \"deployer\" counterpart"
}

2024/05/02-08:46:39.352 - warn: [deployer apis] import only mode, deployer data requested but there is no deployer to ask
2024/05/02-08:46:39.352 - error: [cluster type] unable to get cluster type from deployer, communication error error=import only - deployer is not available
2024/05/02-08:46:39.353 - warn: [startup - cluster type] unable to retrieve cluster type from deployer

 warn: [deployer apis] import only mode, deployer data requested but there is no deployer to ask

2024/05/02-08:52:30.514 - silly: --------------------------------- incoming request ---------------------------------
2024/05/02-08:52:30.514 - info: [WOJ1:FGCJw] New GET request for url: /deployer/api/v3/instance/$iid
2024/05/02-08:52:30.516 - debug: [middle] this api requires deployer, but the "import_only_enabled" setting indicates there is no deployer.
2024/05/02-08:52:30.567 - info: [WOJ1:FGCJw] ended HTTP/1.1 GET /deployer/api/v3/instance/$iid 503 1868 54 ms b89a2
2024/05/02-08:52:30.573 - info: [WOJ1:TXPTU] ended HTTP/1.1 GET /api/v3/migration/status 200 1868 87 ms b89a2

It looks like deployer is a separate package for Ops Console (https://github.com/hyperledger-labs/fabric-operations-console/tree/main/packages/fabric-deployer).
It has separate Docker file (https://github.com/hyperledger-labs/fabric-operations-console/blob/main/packages/fabric-deployer/Dockerfile) and not included to main Ops Console docker file (https://github.com/hyperledger-labs/fabric-operations-console/blob/main/docker/console/Dockerfile).

Also all references to the deployer_url variable inside the Bevel Ops Console container have a default value of http://example.com:80.

Describe the solution you'd like

Implement deployer package into Bevel Ops Console helm chart as separate deployment or as container in Ops Console statefulset.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Issue with the same problem with Ordering Services- hyperledger-labs/fabric-operations-console#594
Issues where the deployer is mentioned as a separate component:
hyperledger-labs/fabric-operations-console#34
hyperledger-labs/fabric-operations-console#583
hyperledger-labs/fabric-operations-console#522

Orderer service communication issue may be preventing channel creation:

[mike18taz]

I am also encountering this issue with Fabric v2.5.11 as I noted in the same related issue.
However, I am seeing the Kubernetes deployer related issues in the browser console when I go to look at the peers as well and they didn't give me any error when setting them up so I don't think that is the culprit.
I am seeing errors related to grpc that definitely look related though:

RestApi: POST /api/v3/proxy/ succeeded with 200: OK [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
*[stitch] building a proposal for getChannelConfigBlockFromOrderer: system-channel [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
*[stitch] building a proposal for getChannelBlockFromOrderer: system-channel start: null stop: null [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
[stitch] received error status in grpc streaming deliver response {
	"status": 404,
	"statusMessage": "grpc code NOT_FOUND = (http code 404) requested entity (e.g. channel, block, file, etc...) was not found",
	"headers": null,
	"message": null,
	"trailers": {
		"headersMap": {
			"grpc-status": [
				"0"
			]
		}
	},
	"_proxy_resp": {
		"status_message": "",
		"code": 0
	},
	"_block_data": null
} [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
[stitch] getChannelBlockFromOrderer was not successful 0 [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
![stitch] error output 
Object { function_name: "getChannelBlockFromOrderer", error: true, msp_id: "OrdererMSP", stitch_msg: "unable to get block: grpc code NOT_FOUND = (http code 404) requested entity (e.g. channel, block, file, etc...) was not found", grpc_resp: {…}, orderer_host: "http://localhost:3000/grpcwp/https%3A%2F%2Fproxy.orderer.example.com%3A7445", _input2stitch: {…} }
[stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)

and then this:

[stitch] getChannelBlockFromOrderer responding with 
Array [ {…} ]
[stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
[stitch] could not find config block number from orderer {
	"function_name": "getChannelBlockFromOrderer",
	"error": true,
	"msp_id": "OrdererMSP",
	"stitch_msg": "unable to get block: grpc code NOT_FOUND = (http code 404) requested entity (e.g. channel, block, file, etc...) was not found",
	"grpc_resp": {
		"status": 404,
		"statusMessage": "grpc code NOT_FOUND = (http code 404) requested entity (e.g. channel, block, file, etc...) was not found",
		"headers": null,
		"message": null,
		"trailers": {
			"headersMap": {
				"grpc-status": [
					"0"
				]
			}
		},
		"_proxy_resp": {
			"status_message": "",
			"code": 0
		},
		"_block_data": null
	},
	"orderer_host": "http://localhost:3000/grpcwp/https%3A%2F%2Fproxy.orderer.example.com%3A7445",
	"_input2stitch": {
		"msp_id": "OrdererMSP",
		"client_cert_b64pem": "LS0tLS1CRUdJTiBDRVJUSUZJQ0FURS0tLS0tCk1JSUNUVENDQWZPZ0F3SUJBZ0lVSWdGNG5ITXdhRGJjL3lmZDlEdCtjN0dxYm0wd0NnWUlLb1pJemowRUF3SXcKWWpFTE1Ba0dBMVVFQmhNQ1ZWTXhFVEFQQmdOVkJBZ1RDRTVsZHlCWmIzSnJNUkV3RHdZRFZRUUhFd2hPWlhjZwpXVzl5YXpFVU1CSUdBMVVFQ2hNTFpYaGhiWEJzWlM1amIyMHhGekFWQmdOVkJBTVREbU5oTG1WNFlXMXdiR1V1ClkyOXRNQjRYRFRJMU1Ea3lOakUzTVRFd01Gb1hEVEkyTURreU5qRTVNREl3TUZvd0p6RU9NQXdHQTFVRUN4TUYKWVdSdGFXNHhGVEFUQmdOVkJBTVRERzl5WkdWeVpYSkJaRzFwYmpCWk1CTUdCeXFHU000OUFnRUdDQ3FHU000OQpBd0VIQTBJQUJCRlV0aWZFbGFJZmlaTTVvQVFiRE5yOGJOVVlTT2M3elN2K2U0Nm1sdGE1d3VaVzZqYnpPRmpVCmdYZnFkSGtMRURhYUVIYVhSazJUWm52cFdBM2ZwT3lqZ2NFd2diNHdEZ1lEVlIwUEFRSC9CQVFEQWdlQU1Bd0cKQTFVZEV3RUIvd1FDTUFBd0hRWURWUjBPQkJZRUZPNDZnMEN6bE9OTk9qNHBlTWhTWHMvSTVDWUtNQjhHQTFVZApJd1FZTUJhQUZCT0hhSk9MNEsrZDBMS2RKR1RkekFRTFFqVDdNRjRHQ0NvREJBVUdCd2dCQkZKN0ltRjBkSEp6CklqcDdJbWhtTGtGbVptbHNhV0YwYVc5dUlqb2lJaXdpYUdZdVJXNXliMnhzYldWdWRFbEVJam9pYjNKa1pYSmwKY2tGa2JXbHVJaXdpYUdZdVZIbHdaU0k2SW1Ga2JXbHVJbjE5TUFvR0NDcUdTTTQ5QkFNQ0EwZ0FNRVVDSVFESApid0pCdjZnRGlIREtPZTh2YndUZDlqRVk3WVdXY3NWRVEwbW4xckxuS1FJZ2VrWCtNR3ZySW9DQU9FYUp4Z1p5ClM1ODhWbVgvMldxWFk3dkhCODl4S2dVPQotLS0tLUVORCBDRVJUSUZJQ0FURS0tLS0tCg==",
		"orderer_host": "http://localhost:3000/grpcwp/https%3A%2F%2Fproxy.orderer.example.com%3A7445",
		"channel_id": "system-channel",
		"start_block": null,
		"stop_block": null,
		"funk": "getChannelBlockFromOrderer"
	}
} [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)
ordererDetails: TypeError: e.channel_group is undefined [stitch-dependencies.min.js:72:4798](http://localhost:3000/stitch-dependencies.min.js)

I also believe that this is causing issues with Channel creation that amozghovyi mentioned as I am seeing the same error and unable to create channels.