feat: extend OncoTree metadata in database and models (#11993)

[Annu881]

Fix #11993

Describe changes proposed in this pull request:
This PR extends the OncoTree metadata support in thetype_of_cancertable by adding additional fields to store versioning and status information. This enables better handling of deprecated or historical OncoTree codes.
Changes include:

1. Extended the type_of_cancer table to include the following columns:

• VERSION
• STATUS
• HISTORY
• URI
  Implemented for both MySQL and ClickHouse schemas.

2. Updated Java model classes to support the new metadata fields:

• TypeOfCancer (legacy domain model)
• CancerType (application model)

3. Modified MyBatis mappers to populate the new fields:

• StudyMapper.xml
• CancerStudyMapper.xml
• CancerStudyMetadataMapper.xml
• ClickhouseCancerStudyMapper.xml

4. Added a MySQL migration script:

    db-scripts/migration.sql (v2.15.0)
   

5. Updated test seed data with sample OncoTree metadata:

• seed_mini.sql
• clickhouse_data_legacy.sql

This allows storing structured OncoTree metadata such as version history and status information, which can help support deprecated OncoTree codes and improve data traceability.

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.
  Verified with:
• CancerTypeMyBatisRepositoryTest
• CancerTypeServiceImplTest
• CancerStudyMetadataExporterTests
  Tested using Java 21
• Is this PR adding logic based on one or more clinical attributes?
  Yes — OncoTree metadata fields (VERSION, STATUS, HISTORY, URI) are clinical classification metadata.
• Make sure your PR has one of the labels defined in https://github.com/cBioPortal/cbioportal/blob/master/.github/release-drafter.yml
  Recommended label: feature

Any screenshots or GIFs?

N/A (Backend change)

Notify reviewers

@inodb @sheridancbio @YashhCanCode

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
42.9% Coverage on New Code
70.6% Duplication on New Code

See analysis details on SonarQube Cloud