Draft: POC[Not to be merged] - Corpus details page

What does this MR do and why?

This POC is to validate the approach before actual implementation.

We are creating the corpus management page.

Following is the plan of action:

1. We will allow users and coverage fuzzing job to upload the corpus file and in the backend, we will save those files as the generic package. We will use the Publish a package endpoint to do so.

2. The next call will go to CreateCorpus Graphql mutation that will take create a corpus record and associate the package with it.

3. The frontend will use the query corpuses to find the corpuses for a particular project and show it on the corpus management page.

Describe in detail what your merge request does and why.

Screenshots or screen recordings

{
  corpuses(projectId: 1){
   nodes{
    	id
  		package{
        name
        packageFiles{
        	nodes{
            fileName
          }
        }
      }
    }  
  }

}

curl --header "PRIVATE-TOKEN: uzsLZ6teL2oWJobTmTJE" \
     --upload-file corpus1_file.txt \
     "http://gitlab.localdev:3000/api/v4/projects/1/packages/generic/corpus1_package/0.0.1/corpus1_file.txt?status=hidden"

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

#341218 (closed)