Refactor old cc pkg upload API

[xichen1]

Refactor old chaincode package upload API according to the new design doc.

Signed-off-by: xichen1 xichen.pan@gmail.com

[xichen1]

The original API implementation requires the user to upload a zipped chaincode file, then the backend will package the the cc file using peer command line.

According to our new API design, now we need the user to package the cc package by themselves and upload the cc package directly. Therefore adjust the current implementation to allow the requirement.

The PR also updated the cc Django model, the current db columns include uuid, package_id, name, label, version, creator, language, description and create_ts.

[xichen1]

One issue still exists is it's impossible to get cc version from the metadata.json file (it doesn't contain the version info).

Do we update the version in the backend automatically? (if a duplicate cc package id is received we increase the version?)

Update: It seems cc name and version can only be created in Approve step (to create a new running instance), which needs to be confirmed.

[xichen1]

Need to simplify the extraction and verification steps. Only need to extract metadata.json file and check and store its information. It can be done using the library tarfile:

    with tarfile.open(tar_file_path, "r:gz") as tar:
        try:
            # Retrieve the member information for the specified file
            member = tar.getmember("metadata.json")
            # Extract the file
            tar.extract(member, path=output_path)
        except KeyError:
            print(f"File '{file_name}' not found in the archive.")

[xichen1]

One issue still exists is it's impossible to get cc version from the metadata.json file (it doesn't contain the version info).

Do we update the version in the backend automatically? (if a duplicate cc package id is received we increase the version?)

Update: It seems cc name and version can only be created in Approve step (to create a new running instance), which needs to be confirmed.

Confirmed: cc names and versions are decided at Approve step. They are tied with the cc and one channel specified at Approve step.