fix(timeouts): clear timeouts created in componentDidLoad

[KillerCodeMonkey]

Issue number: resolves #30860

What is the current behavior?

We have flaky tests in an ionic angular project that root cause are not cleaned up timeouts.
I commented out the timeout in the searchbar componentWillLoad method. and after several runs no flaky tests at all.

My guess -> test runs faster than the 300ms it takes til the timeout runs. Everything is cleaned up, but not the ionic timeouts (i think i saw something similar in other components)

What is the new behavior?

Timeouts are cleaned on disconnect.

Does this introduce a breaking change?

• Yes
• No

Other information

Testrunner is vitest + angular 20 and latest ionic version 8.x

[vercel]

@KillerCodeMonkey is attempting to deploy a commit to the Ionic Team on Vercel.

A member of the Team first needs to authorize it.

[KillerCodeMonkey]

@ShaneK

lint + build work locally.

but one test is failing:

src/components/datetime/test/disabled/datetime.spec.tsx
  ● ion-datetime disabled › picker should be disabled in prefer wheel mode

    expect(received).toEqual(expected) // deep equality

    Expected: 4
    Received: 3

      31 |     const columns = datetime.shadowRoot!.querySelectorAll('ion-picker-column');
      32 |
    > 33 |     await expect(columns.length).toEqual(4);
         |                                  ^
      34 |
      35 |     columns.forEach((column) => {
      36 |       expect(column.disabled).toBe(true);

      at Object.<anonymous> (src/components/datetime/test/disabled/datetime.spec.tsx:33:34)

but it fails with clean master as well.

[thetaPC]

@KillerCodeMonkey Thank you for the pull request!

In order for us to move forward, we need this PR to have a linked issue. Please submit one with a minimal repro, thanks!

[KillerCodeMonkey]

How to create a repro repository on possible flaky tests and not cleaned up timeouts?

I mean this is just how to work with timeouts, intervals? Clean them up when not needed anymore to avoid side effects. And prevent memory leaks.

So how should i be able to create a repro repo?

There are already some cleanups in the code in other components...
It is just not done everywhere.

Greets

[thetaPC]

@KillerCodeMonkey I agree that we should clean up the timeouts and we appreciate your work on this! However, if you can provide a reproduction of what you have even if it's flaky. By providing an official issue, we can verify that we haven't missed anything else. We might end up finding more issues related to timeouts during triage that we can keep tabs of.

[thetaPC]

@KillerCodeMonkey don't worry too much on providing a repro. The most important thing is to create the issue, thanks!

[KillerCodeMonkey]

i just created a clean issue and not a bug to avoid to set the required repo url field. i hope this is okay #30860

[thetaPC]

That should be fine! Thank you so much!!