feat: add TAG105 to block tagging.taggable changing from false to true

[zhaomicx]

Issue

TAG101 blocks tagging.taggable going from true to false, but the inverse transition (false -> true) had no check.

Description of changes

Adds TAG105 - "tagging.taggable MUST NOT change from false to true".

This required restructuring the taggable branch of ensure_taggable_not_changed rather than just appending a clause. The branch asserted this.old_value == true as a bare clause with no custom message attached (the << ... >> block binds to the clause that precedes it, i.e. this.new_value != false). Because clauses in a block are ANDed, a false -> true flip already failed the rule today - but the resulting finding carried an empty message and was silently dropped by runner.py, which skips message-less checks. The violation surfaced in neither non_compliant, compliant, nor skipped.

Turning old_value into a when condition fixes that and lets each direction carry its own check id:

when this.property == "/tagging/taggable" {
    when this.old_value == true  { this.new_value != false << TAG101 >> }
    when this.old_value == false { this.new_value != true  << TAG105 >> }
}

TAG101 behavior is unchanged - same check id, message and reported path (/tagging/changed/0/new_value).

Testing

Verified against the engine for every transition: false -> true reports TAG105 only; true -> false reports TAG101 only; no-op and newly-added tagging blocks report nothing; TAG102/TAG104 unaffected. Two integ cases added (the minimal flip, plus the realistic case where a provider turns taggable on while adding tagOnCreate/tagUpdatable/cloudFormationSystemTags/tagProperty in the same revision).

Full suite 96 -> 98 passing, black==22.3.0 clean, pylint==2.15.10 at 10.00/10.

Follow-up (not in this PR)

TAG102 (tagOnCreate) and TAG103 (cloudFormationSystemTags) still have the same message-less-clause pattern, so a false -> true flip on either makes the rule fail with nothing reported. Happy to apply the same two-line restructure in a separate PR.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.