Add missing 'CHASSIS' key to some Thunderbolt MTF files

[juk0de]

This PR adds the string CHASSIS to the systemmanufacturer key of the following MTF files:

• Thunderbolt_TDR-7M
• Thunderbolt_TDR-7S
• Thunderbolt_TDR-7SE
• Thunderbolt_TDR-8M
• Thunderbolt_TDR-9M
• Thunderbolt_TDR-9NAIS
• Thunderbolt_TDR-9Nr
• Thunderbolt_TDR-9T

I encountered this issue while working on my MTF to JSON converter. Initially, I thought it was just an inconsistency, but these eight files are the only biped mech files missing the CHASSIS string. Therefore, I believe it is an ordinary bug, so I decided to fix it.

[IllianiCBT]

Congratulations on your first PR for this project!

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 0.52%. Comparing base (78b9c66) to head (1e50c58).
Report is 7 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff            @@
##             master   #1564   +/-   ##
========================================
  Coverage      0.52%   0.52%           
  Complexity       49      49           
========================================
  Files           265     265           
  Lines         30440   30440           
  Branches       5182    5182           
========================================
  Hits            160     160           
  Misses        30239   30239           
  Partials         41      41           

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

[HammerGS]

I'll merge this, but for future reference all units file (BLK/MTF) are managed via MegaMek repo.

[juk0de]

I'll merge this, but for future reference all units file (BLK/MTF) are managed via MegaMek repo.

Understood 👍 Will create the next MTF related PR against MegaMek. But the MTF files are fundamentally identical between MegaMek and MegaMekLab, right?

[HammerGS]

The master data repo is MegaMek and stays current. We only transfer the MM units to MML and MekHQ every few weeks and it's a manual process which is why we always use MM as the primary data repo.

[juk0de]

Sounds complicated... Do I have to make another PR against MegaMek for these changes or are you going to transfer them manually?

[HammerGS]

I’ve merged these and moved them the other way. In future make against MM