Add popEVE links to variant page

[northwestwitch]

This PR adds a functionality or fixes a bug.

• Closes Add popEVE link to the RefSeq transcripts table #6013

Testing on cg-vm1 server (Clinical Genomics Stockholm)

Prepare for testing

1. Make sure the PR is pushed and available on Docker Hub
2. First book your testing time using the Pax software available at https://pax.scilifelab.se/. The resource you are going to call dibs on is scout-stage and the server is cg-vm1.
3. ssh <USER.NAME>@cg-vm1.scilifelab.se
4. sudo -iu hiseq.clinical
5. ssh localhost
6. (optional) Find out which scout branch is currently deployed on cg-vm1: podman ps
7. Stop the service with current deployed branch: systemctl --user stop scout@<name_of_currently_deployed_branch>
8. Start the scout service with the branch to test: systemctl --user start scout@<this_branch>
9. Make sure the branch is deployed: systemctl --user status scout.target
10. After testing is done, repeat procedure at https://pax.scilifelab.se/, which will release the allocated resource (scout-stage) to be used for testing by other users.

Testing on hasta server (Clinical Genomics Stockholm)

Prepare for testing

1. ssh <USER.NAME>@hasta.scilifelab.se
2. Book your testing time using the Pax software. us; paxa -u <user> -s hasta -r scout-stage. You can also use the WSGI Pax app available at https://pax.scilifelab.se/.
3. (optional) Find out which scout branch is currently deployed on cg-vm1: conda activate S_scout; pip freeze | grep scout-browser
4. Deploy the branch to test: bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_scout -t scout -b <this_branch>
5. Make sure the branch is deployed: us; scout --version
6. After testing is done, repeat the paxa procedure, which will release the allocated resource (scout-stage) to be used for testing by other users.

How to test:

1. how to test it, possibly with real cases/data

Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.

Review:

• code approved by
• tests executed by CR

[codecov]

Codecov Report

❌ Patch coverage is 71.42857% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 83.88%. Comparing base (a49902c) to head (b073788).

Files with missing lines	Patch %	Lines
scout/server/links.py	71.42%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6016      +/-   ##
==========================================
- Coverage   83.88%   83.88%   -0.01%     
==========================================
  Files         336      336              
  Lines       21022    21029       +7     
==========================================
+ Hits        17635    17640       +5     
- Misses       3387     3389       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[northwestwitch]

Marking this one as ready for review. Note that:

• the only way to build a direct link to popEVE would be using RefSeq protein IDs (can't use genes or transcript RefSeqs, even if these are searchable in the portal).
• This is very limiting unfortunately, because NOT all links will work, since popEVE won't contain all protein RefSeq IDs.

One could increase the chances of finding the right prot RefSeq possibly by adding the link only for build 38 I guess? We could also not add the link at all since it won't work in many cases.. Any suggestions?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube Cloud