hyperledger

When deploying fabric in enterprise's intranet (without the ability to access internet), users maybe upload chaincode builder images and chaincode runtime images to a private docker registry which requires authentication when pulling images.
I think fabric can support this scenario by adding configuration in chaincode section of core.yaml, such as:

chaincode:
    registry:
        

Currently I2::Dev::Tests workflow has 2 different testing jobs (tests_with_coverage and integration_tests) and has some duplicated compilation cost.

One solution will be:

• Replace #[cfg(not(coverage))] with #[no_coverage] on integration modules once #[no_coverage] become stable
• Remove `integration_t

The tails file location after publishing a credential definition is not considering the white spaces in revocation tags, which leads to fail in uploading tails file but publishes the credential definition on the ledger