Endpoints to get the md5 hash of the original model file

[carmenfan]

Description

Product issue: https://github.com/3drepo/3D-Repo-Product-Team/issues/547

To add endpoints for federation/containers to provide the md5 hash of the original files

Additional endpoints

route: HTTP GET /teamspaces/{teamspace}/projects/{project}/containers/{container}/revisions/{revision}/files/original/info
description: get the details of the original file uploaded to that revision of the container
permissions: viewer+
response: md5 hash of the original file

{
    container: "<container ID>",
    code: "<revision code>",
    uploadedAt: 223984739284723, // timestamp of when it was uploaded
    hash: "<md5 hash of the original file uploaded to this revision>",
    filename: "abc.rvt",
    size: 329487234 // size in Bytes
}

route: HTTP GET /teamspaces/{teamspace}/projects/{project}/federations/{federation}/revisions/{revision}/files/original/info
description: get the details of the original file uploaded to all the containers within the federation
permissions: viewer+
response: md5 hash of the original file

[{
    container: "<container ID>",
    code: "<revision code>",
    uploadedAt: 223984739284723, // timestamp of when it was uploaded
    hash: "<md5 hash of the original file uploaded to this revision>",
    filename: "abc.rvt",
    size: 329487234 // size in Bytes
},
{
    container: "<container ID>",
    code: "<revision code>",
    uploadedAt: 223984739284723, // timestamp of when it was uploaded
    hash: "<md5 hash of the original file uploaded to this revision>",
    filename: "def.dwg",
    size: 329487234 // size in Bytes
}]

NOTE:

• for each of the container, we need to make sure the user has at least viewer permissions to the container. if not, we should omit the information about that container.

Goals

• As a user, I want to be able to get detailed information about the original file of a model, so I can verify if the same file is being used in applications outside of 3D Repo.
• As a admin, I want to make sure information about the files are not leaked to users who do not have at least viewer permission to the container.

Tasks

• create route for containers
  • validate that user can access it - throw 403 if not allowed
  • retrieve the original files
  • MD5 hash them
  • create response
• create route for federations
  • validate that user can access - throw 403 if not allowed
  • return list of items and the original files
  • MD5 hash the files
  • create response