Bypass SwiftLint using ACTION instead of CONFIGURATION

[mokagio]

Follows up on
#23996 (comment)

Makes the logic more precise, given the error occurs when archiving.

To test: One can only test this locally because we bypass the SwiftLint build phase in CI in favor of the dedicated linter.

Here are screenshots from my local machine:

_A successful build, including SwiftLint_

Important

One of the prototype builds failed, but the error is about is at the AppCenter level

Regression Notes

1. Potential unintended areas of impact – N.A.
2. What I did to test those areas of impact (or what existing automated tests I relied on) – N.A.
3. What automated tests I added (or what prevented me from doing so) – N.A.

---

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes. N.A.
• I have considered adding accessibility improvements for my changes. N.A.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary. N.A.

UI changes testing checklist: Not a UI PR.

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress Alpha by scanning the QR code below to install the corresponding build.

	App Name	WordPress Alpha
	Configuration	Release-Alpha
	Build Number	pr24094-32ed02f
	Version	25.7.1
	Bundle ID	org.wordpress.alpha
	Commit	32ed02f
	App Center Build	WPiOS - One-Offs #11517

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack Alpha by scanning the QR code below to install the corresponding build.

	App Name	Jetpack Alpha
	Configuration	Release-Alpha
	Build Number	pr24094-32ed02f
	Version	25.7.1
	Bundle ID	com.jetpack.alpha
	Commit	32ed02f
	App Center Build	jetpack-installable-builds #10549

Automatticians: You can use our internal self-serve MC tool to give yourself access to App Center if needed.