feat(macOS): enable tests in NextcloudDev builds.

[camilasan]

Resolves

Build the tests by default.

Checklist

• Sign-off message is added to all commits.
• The commit history is clean with no merge commits.
  • How to rebase your commits
  • How to squash commits with rebase
• Uploaded screenshots from before and after for UI changes.
• Documentation has been updated or is not required.
• Backports requested where applicable (critical bugfixes).
• Labels added where applicable (bug/enhancement).
• Milestone added for target version.

AI (if applicable)

• The content of this PR was partly or fully generated using AI
  • I have read the guidelines for AI-assisted contributions.
  • I have read Nextcloud's AI Contribution Policy.

[github-actions]

Artifact containing the AppImage: nextcloud-appimage-pr-10167.zip

Digest: sha256:fe868b4385833033debe53132d93b036d13b7b8223f16fbe83fa3916da5472b2

To test this change/fix you can download the above artifact file, unzip it, and run it.

Please make sure to quit your existing Nextcloud app and backup your data.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[i2h3]

But why? There is no need for them here. This shell script and the Xcode workspace have the purpose for developers to build, run and debug the app and its extensions on macOS. Including the mostly unnecessary build (none are run, as far as I can tell) of Craft test target will slow down the feedback loop.

The file provider extension code is tested differently by selecting the NextcloudFileProviderKit package scheme and running the Xcode test action.

To build and run the Craft blueprint tests Xcode, this scheme and shell script can be completely circumvented, invoking mac-crafter directly.