feat: Add exclusions and exclusion categories to gunmods

[KheirFerrum]

Purpose of change

• Expansion of Weapon Categories for gunmods. #2541

Allow further fine-tuning of what guns can and cannot be installed with specific gunmods, both for further development and specificity of vanilla gunmods and for the use of mod authors.

Describe the solution

Adds mod_exclusions and mod_exclusion_category as optional fields in gunmods. This allows contributors to add specific blacklists (say you want to make a gun mod installable on all rifles except the Rivtech battlerifle for instance), and blacklist categories (all rifles unless they are energy weapons).

Blacklists take priority over target categories but not target ids. Priority for inclusion/exclusion goes mod_targets > mod_exclusions > mod_exclusion_category > mod_target_category

Note that it will scream at you if you try to include and exclude the same id or the same set of categories.

Changes the gyroscopic stabilizing system as a proof of concept for this system, and to ensure it's used somewhere in the vanilla game to avoid it being lost to time.

Describe alternatives you've considered

Testing

• Spawn an A7 laser rifle, a gyroscopic stabilizer and a modified gyroscopic stabilizer.
• Check that modified gyroscopic stabilizer is installable but gyroscopic stabilizer is not
• Alter entry of gyroscopic stabilizer so it has mod_targets and mod_exclusions for laser_rifle, and extend mod_target_category to include ENERGY_WEAPONS
  • Check that error message screams at you for doing this twice (once for mod_targets and mod_exclusions and once for mod_target_category and mod_exclusion_category)
  • Check that you can install the gyroscopic stabilizer now.
• Check that if you supply invalid ids to mod_exclusion and mod_exclusion_category it screams at you.

Additional context

Not ideal to be using gyroscopic stabilizers as the proof of concept, but I can't think of anything that I can even remotely justify as an example right now. Maybe someone can look over the gunmods to see if anything nonsensical jumps out.

Checklist

• Document the changes in the appropriate location in the doc/ folder.
• If documentation for this feature does not exist, please write it or at least note its lack in PR description.
• New localizable fields need to be added to the lang/bn_extract_json_strings.sh script if it does not support them yet. (?)
• If applicable, add checks on game load that would validate the loaded data.

[autofix-ci]

The Autofix app has found code style violation and automatically formatted this Pull Request.

I locally edit my commits (e.g: git, github desktop)

Please choose following options:

I'd like to accept the automated commit

1. Run git pull. this will merge the automated commit into your local copy of the PR branch.
2. Continue working.

I do not want the automated commit

1. Format your code locally, then commit it.
2. Run git push --force to force push your branch. This will overwrite the automated commit on remote with your local one.
3. Continue working.

If you don't do this, your following commits will be based on the old commit, and cause MERGE CONFLICT.

This PR is complete and I don't want to edit it anymore

It's safe to ignore this message.

I edit this PR through web UI

You can ignore this message and continue working.

I have no idea what this message is talking about

You can ignore this message and continue working. If you find any problem, please ask for help and ping @scarf005.

[scarf005]

additional screenshots

[scarf005]

might make sense to rename it to excluded.

[KheirFerrum]

Sorry, how so?

[scarf005]

because this line is highly confusing?

            if( usable || unusable ) {

[KheirFerrum]

Ah, I thought you were talking about "exclusion".