Remove "supress"

[kasanari]

Not sure what this is a remain of, but I am not using it and it seems to overlap in functionality with actionability.

[kasanari]

A test failed, so it is apparently supporting something...

[mrkickling]

coreLang uses it as a tag on certain defenses to hide them. Should we just ignore the tag?

[kasanari]

My feeling would be that since that is CoreLang-specific, any user that needs that behavior could create their scenarios with action-ability based on the tags. I do not like the thought of the simulator having checks that are specific to CoreLang, but perhaps the 'suspend' check can be moved to the scenario creation code where it gets converted into actionability.

[mrkickling]

I can add actionability to the affected scenarios and see if the tests pass

[mrkickling]

Did it now. But this could be seen as a breaking change since coreLang users that do not use actionability will get new actions in their defense surface once we release this.