Add support for Fabric v2.5 LTS release

The upgrade from 2.X to 2.5 shouldn't be problematic, based on the official docs: https://hyperledger-fabric.readthedocs.io/en/release-2.5/upgrade_to_newest_version.html

The versions of the Fabric components are here.

https://github.com/hyperledger/firefly-cli/blob/main/internal/blockchain/fabric/constants.go

Context:

The fabric tools image is a problem because they have changed the location of the FABRIC_CONFIG folder.

https://hub.docker.com/layers/hyperledger/fabric-tools/2.5/images/sha256-ae29de91b84[…]19a8d35b234b9a39d6ffb069b551dc8c0fd6c38ea8e0e?context=explore
vs
https://hub.docker.com/layers/hyperledger/fabric-tools/2.4/images/sha256-b1194f50908[…]355d119fbb8dfef8b2d78954eabd7d221a39fc90bb850?context=explore

Also that image is deprecated anyhow. Not sure if it will be better to change the logic in Firefly code or just create a custom image with the same settings as the 2.4.0 version

_"The fabric-tools docker image is deprecated and may be removed
The fabric-tools docker image will not be published in future Fabric releases.
Instead of using the fabric-tools docker image, users should utilize the
published Fabric binaries. The Fabric binaries can be used to make client calls
to Fabric runtime components, regardless of where the Fabric components are running."_

https://github.com/hyperledger/fabric/releases
https://github.com/hyperledger/fabric/releases/tag/v2.5.4