Let borg modules exclude other modules

[korczoczek]

About the PR

Added functionality for borg modules to define modules they are incompatible with, as in they won't install if certain modules are already installed.

Demonstrated by making the regular laser and heavy laser modules mutually exclusive, though i will leave labeling the rest of the modules to the discretion of the xenoborg workgroup

Why / Balance

Resolves #43090
Needed functionality for restricting xenoborgs to a single weapon module only

Technical details

Added fields to BorgModuleComponent for defining what the module's type is and which types it is incompatible with
Added an extra check during module insertion to see if the chassis contains am incompatible module
Added extra examine text for modules which are incompatible with other modules
Made the Laser and Heavy Laser modules incompatible as a showcase

Media

2026-03-17.21-16-27.mp4

Requirements

• I have read and am following the Pull Request and Changelog Guidelines.
• I have added media to this PR or it does not require an in-game showcase.

Breaking changes

Changelog

[slarticodefast]

Huh, didn't we have another PR for this already?
Let me try to find it.

Also probably should have #41586 merged first.

[korczoczek]

That's strange, i could've sworn i couldn't install duplicate modules during testing, but now i'm unsure

And also too cozy under me covers to check it again

[arenaconspiracy]

Not quite a duplicate, but superceded by #42574 which achieves this and more.

Edit: nevermind, it actually NECESSITATES 2 modules of the same kind be present to swap them out, so this actually conflicts with #42574 , which achieves the opposite.

[korczoczek]

I wouldn't say it conflicts with the other pr per say, as both module exclusivity and the ability to upgrade the default modules are features requested by the silicon/xenoborg workgroup

For this pr i opted to make the two laser weapon of the heavy xeno exclusive to one another, mostly because in contrast to crewborgs xenos can actually eject all their default modules from the get go.

If anything the other pr doesn't go far enough imo, the modules should switch out automatically when an "upgraded" module gets installed instead of just letting you remove the old one manually