Use consistent KDS imports across the whole Kolibri

[PR4NJ41]

This PR addresses the goal of standardizing Kolibri Design System (KDS) logic imports across the codebase. The approach is to import KDS Components directly instead of using Core API.

This PR solves the issue #11561.

References

Please see Issue #11561 and #5488

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included
• Critical user journeys are covered by Gherkin stories
• Critical and brittle code paths are covered by unit tests

PR process

• PR has the correct target branch and milestone
• PR has 'needs review' or 'work-in-progress' label
• If PR is ready for review, a reviewer has been added. (Don't use 'Assignees')
• If this is an important user-facing change, PR or related issue has a 'changelog' label
• If this includes an internal dependency change, a link to the diff is provided

Reviewer checklist

• Automated test coverage is satisfactory
• PR is fully functional
• PR has been tested for accessibility regressions
• External dependency files were updated if necessary (yarn and pip)
• Documentation is updated
• Contributor is in AUTHORS.md

[github-actions]

Build Artifacts

Asset type	Download link
PEX file	kolibri-0.16.0b10.dev0_git.599.gb5e25be4.pex
Windows Installer (EXE)	kolibri-0.16.0b10.dev0+git.599.gb5e25be4-unsigned.exe
Debian Package	kolibri_0.16.0b10.dev0+git.599.gb5e25be4-0ubuntu1_all.deb
Mac Installer (DMG)	kolibri-0.16.0b10.dev0+git.599.gb5e25be4-0.3.0.dmg
Android Package (APK)	kolibri-0.16.0b10.dev0+git.599.gb5e25be4-0.1.0-debug.apk
TAR file	kolibri-0.16.0b10.dev0+git.599.gb5e25be4.tar.gz
WHL file	kolibri-0.16.0b10.dev0+git.599.gb5e25be4-py2.py3-none-any.whl

[MisRob]

Thank you, @PR4NJ41, all good. Code changes make sense and haven't noticed any issues while navigating Kolibri. Just leaving one small note that'd be good to address before merging.

[MisRob]

Thank you @PR4NJ41, all good.

I don't think that the documentation check failure is related to this work. I will look into it first though before merging pull requests.

[rtibbles]

@MisRob yes, the build failure is fixed in develop, and is not caused by this PR, so we can merge this!

[rtibbles]

Great work!