fix(typo): correct spelling in comments and strings

[jannikbx]

Summary

Fixes 42 spelling errors in code comments, documentation and strings across the server codebase.

Changes

File	Correction
apps/appstore/src/composables/useAppIcon.ts	categroy → category
apps/appstore/src/service/app-discover.ts	useable → usable
apps/dav/lib/CalDAV/EventReader.php	evaludate → evaluate (5×), interation → iteration (4×)
apps/dav/lib/Command/ImportCalendar.php	writeable → writable (2×)
apps/dav/lib/Connector/Sabre/DavAclPlugin.php	writeable → writable
apps/files_sharing/src/components/SidebarTabExternal/SidebarTabExternalSection.vue	TOOD → TODO
apps/files_sharing/src/services/SharingService.spec.ts	exampe → example (2×)
apps/files_versions/src/components/VirtualScrolling.vue	wont → won't
apps/files_versions/tests/VersioningTest.php	secons → seconds (6×)
apps/theming/README.md	inbetween → in between, orginal → original (2×)
apps/theming/lib/Service/BackgroundService.php	whith → with
apps/theming/lib/Util.php	Calculat → Calculate
apps/theming/src/components/AdminSectionAppMenu.vue	wrapps → wraps
core/Service/LoginFlowV2Service.php	successfull → successful
core/src/OC/msg.ts	Displayes → Displays (6×)
core/src/ajax-cron.ts	successfull → successful
lib/private/Mail/Mailer.php	enforcable → enforceable
lib/private/Mail/Message.php	curently → currently, Adresses → Addresses, exsists → exists
lib/private/Mail/Provider/Manager.php	initilize → initialize (2×)
lib/private/Session/CryptoSessionData.php	Wheater → Whether
lib/public/IUserManager.php	whithin → within

All changes are limited to comments, documentation and strings only — no functional impact.

AI Assistance

This contribution was made with the help of DeepSeek V4 Pro and was reviewed by a human.

Assisted-by: DeepSeek:V4-Pro

[jannikbx]

Hi maintainers, I've rebased this PR onto the latest master. The remaining CI failures (filesdrop test, check-ai-trailers) look unrelated to these typo-only changes. Anything else needed from my side to get this merged? Thanks!

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

[ChristophWurst]

The node error is related. Frontend needs rebuilding

[ChristophWurst]

/compile amend /

[jannikbx]

Hi @ChristophWurst, thanks for the hint! I noticed the /compile amend command got a ❌ – it looks like the compile bot is disabled for fork PRs (this PR comes from my fork jannikbx/server). Since the bot could not run, I rebuilt the frontend assets manually on top of the latest master and pushed the recompiled dist files, which also resolves the merge conflicts. However, my local build environment may not be byte-identical to the CI, so the NPM build check might still differ. Could you run the build on the main repo side (or take over the branch) so the assets are compiled in the CI environment? Let me know if anything else is needed. Thanks!