fixrule (input_label_visible) should not trigger when button input contains visible text

[philljenkins]

The original violation in #2122 is correctly no longer triggering.

However, I'm seeing a couple "Needs Review" issues that should not trigger on this Carbon AI page
AILabel component

DOM:

<button 
   aria-expanded="false" aria-controls="id-:r4m:" aria-label="AI Show information" 
   type="button" 
   class="cds--toggletip-button cds--ai-label__button cds--ai-label__button--mini cds--ai-label__button--default">
      <span class="cds--ai-label__text">AI</span>
</button>

1. The text "AI" is correctly part of the button and is displayed, but the rule still triggers.
2. Checker rule input_label_visible is incorrectly reporting against two requirements (SCs). It seems that the single potential reason is triggered, but reported twice. I think neither should be reported:
   • 2.5.3 Label in Name: Needs review: The input element does not have an associated visible label
   • 3.3.2 Labels or Instructions: Needs review: The input element does not have an associated visible label

Triggered by

Rule ID: input_label_visible[file not changed in the PR #2170 ]
Reason ID: potential_no_label

rulesets: [{
        "id": ["IBM_Accessibility", "IBM_Accessibility_next", "WCAG_2_1", "WCAG_2_0", "WCAG_2_2"],
        "num": ["2.5.3", "3.3.2"], //map to both requirements in help
        "level": eRulePolicy.VIOLATION,
        "toolkitLevel": eToolkitLevel.LEVEL_ONE

[philljenkins]

Use this test case to reproduce
Use the following button HTML structure in this URL https://cr2463.csb.app/
A button with text should not require another visible text label.

Triggered by
Rule ID: input_label_visible[file not changed in the PR https://github.com//pull/2170 ]
Reason ID: potential_no_label

After rule fixed in #2146, violation is correctly no longer triggered on 1st example, however, a violation is now incorrectly triggered on 2nd example that was previously not triggered:

before rule fixed in #2146, violation is incorrectly triggered, but not triggered on 2nd correct example: