Chore: Removing integration tests

[brustolin]

Both Alamofire and Home Assistant integration tests are causing more trouble then helping, we will remove this CI tests.

#skip-changelog

[philipphofmann]

Before we can merge this, I think we should

1. Add an entry to the internal decision log
2. Add critical files we shouldn't change by mistake to no-changes-in-high-risk-files.sh.
3. The failure message in no-changes-in-high-risk-files.sh should point you to make test-alamofire and make test-homekit.

Maybe doing some of these steps in subsequent PRs is also okay. Up to you.

[armcknight]

I'll admit I haven't really looked at their results; what issues do they cause? Is it something we could run only after merging to main instead of for every PR push?

[brustolin]

Is it something we could run only after merging to main instead of for every PR push?

TBH, I cant figure it out the problem, this tests went from working flawlessly to failing every time in CI with no apparent reason.
I don't think the headache worth keeping this tests.

[philipphofmann]

@armcknight, we have had these integration tests for roughly a year, and they didn't surface any bugs in our code. We have them to ensure we are not breaking the functionality of UIViewControllers, NSURLSession, NSData, after swizzling. Right now, we know that the swizzling is working fine, and we didn't have to touch the swizzling logic for a year or so. Instead of maintaining these integration tests, we decided to lock these files with no-changes-in-high-risk-files. The next time we have to do some changes, we can add the integration tests again or run them manually.

[philipphofmann]

Thanks for doing this @brustolin 👏

[philipphofmann]

Thanks @brustolin 👍. LGTM