RFC83: Add admin call to make virtual study available for all users on their landing pages

[forus]

Fix # (see https://help.github.com/en/articles/closing-issues-using-keywords)

Describe changes proposed in this pull request:

• Introduce an admin call, secured by a secret key, to publish virtual studies for all users, making them visible on the landing page.

Frontend cBioPortal/cbioportal-frontend#4923

Checks

• The commit log is comprehensible. It follows 7 rules of great commit messages. We can fix this during merge by using a squash+merge if necessary
• Has tests or has a separate issue that describes the types of test that should be created. If no test is included it should explicitly be mentioned in the PR why there is no test.
• Is this PR adding logic based on one or more clinical attributes? If yes, please make sure validation for this attribute is also present in the data validation / data loading layers (in backend repo) and documented in File-Formats Clinical data section!
• Make sure your PR has one of the labels defined in https://github.com/cBioPortal/cbioportal/blob/master/.github/release-drafter.yml

Any screenshots or GIFs?

If this is a new visual feature please add a before/after screenshot or gif
here with e.g. Giphy CAPTURE or Peek

Notify reviewers

Read our Pull request merging
policy. It can help to figure out who worked on the
file before you. Please use git blame <filename> to determine that
and notify them either through slack or by assigning them as a reviewer on the PR

[haynescd]

Lastly just try to address as much as the sonar cloud issues as possible

[forus]

Lastly just try to address as much as the sonar cloud issues as possible

@haynescd please have another look. The last 2 sonar cloud issues are intended. There is ticket for fixing those #10843

[forus]

@haynescd Please have a look into docs 3ca2a7b

[forus]

@pieterlukasse Please check these extras 162e5a4

[pieterlukasse]

Looks good. One final question: what guarantees that
test5UnpublishVirtualStudy, test6NoPublicVirtualStudiesAfterRemoval, test7UnpublishedVirtualStudyExists execute in sequence?

[forus]

Looks good. One final question: what guarantees that test5UnpublishVirtualStudy, test6NoPublicVirtualStudiesAfterRemoval, test7UnpublishedVirtualStudyExists execute in sequence?

@FixMethodOrder(MethodSorters.NAME_ASCENDING) at the top of the test class.

[haynescd]

LGTM

[sonarcloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
74.4% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud