Frag - Add public blacklist interface

[lambdatiger]

This PR is based on PR #10157 and requires it to be merged.

When merged this pull request will:

• Adds a public function (addClassBlacklist) to blacklist ammo classes from producing fragments, spall, or both.
• Changes the current blacklist function to be public and adds some param checks.

Feedback on the wording for the function descriptions is most welcome (and the code itself)!

IMPORTANT

• If the contribution affects the documentation, please include your changes in this pull request so the documentation will appear on the website.
• Development Guidelines are read, understood and applied.
• Title of this PR uses our standard template Component - Add|Fix|Improve|Change|Make|Remove {changes}.

[johnb432]

This should be placed in the "arguments" section.
The two sentences here are useless imo, last sentence is useful info ('Once an...').

[lambdatiger]

I always felt confused and under explained when reading the ACE documentation, but that's probably a me thing. I'll move relevant information to the arguments/example and delete the rest. Let me know if that's still too much

[LinkIsGrim]

Naming is a bit weird to me: add implies you can only add to the blacklist, not remove from it. set would be more appropriate I think

That being said, it's trivial. Anyone touching this is going to read the docs, and if a class is being added then removed from the blacklist, there's some bad decisions being made somewhere.

[lambdatiger]

Naming is a bit weird to me: add implies you can only add to the blacklist, not remove from it. set would be more appropriate I think

That being said, it's trivial. Anyone touching this is going to read the docs, and if a class is being added then removed from the blacklist, there's some bad decisions being made somewhere.

Sure, would you say modifyClassBlacklist? Or do you have suggestions?

[LinkIsGrim]

Naming is a bit weird to me: add implies you can only add to the blacklist, not remove from it. set would be more appropriate I think
That being said, it's trivial. Anyone touching this is going to read the docs, and if a class is being added then removed from the blacklist, there's some bad decisions being made somewhere.

Sure, would you say modifyClassBlacklist? Or do you have suggestions?

setClassBlacklisted makes the most sense to me, set indicating that it can both black/white-list while also indicating that we're not setting the blacklist itself, just the state of that class

[lambdatiger]

Missed some semicolons on function return values