Should spec repo be banned from using disable: in tspconfig.yaml

Some spec have used that as a shortcut to not doing inline suppression. PRoblem is this rule now won't flag any new bad pattern that are not excluded for back compat.

The issue points to tspconfig.yaml and uses of disable: in spec files; start by auditing those configurations and the rule that consumes them. Done means an agreed policy is applied so backward-compatible exclusions do not hide newly introduced bad patterns.

Written by the indexing model from the issue text.