fix: scss import warning

[kyangconn]

通过cherry-pick dev分支中的修复提交，让lint不再向scss中的@import哈气。

Modifications / 改动点

• This is NOT a breaking change. / 这不是一个破坏性变更。

Screenshots or Test Results / 运行截图或测试结果

---

Checklist / 检查清单

• 😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
  / 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。

• 👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
  / 我的更改经过了良好的测试，并已在上方提供了“验证步骤”和“运行截图”。

• 🤓 I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in requirements.txt and pyproject.toml.
  / 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到 requirements.txt 和 pyproject.toml 文件相应位置。

• 😮 My changes do not introduce malicious code.
  / 我的更改没有引入恶意代码。

Summary by Sourcery

Update SCSS styling entrypoint and partials to use the modern @use syntax and ensure shared variables are properly imported.

Bug Fixes:

• Resolve lint warnings related to deprecated @import usage in SCSS files.

Enhancements:

• Standardize SCSS module imports across layout and component styles by switching to @use and explicitly including the shared variables module.

[sourcery-ai]

Hey - I've left some high level feedback:

• Since many partials now @use '../variables' as *;, consider creating a central variables module that @forwards your tokens and @uses that instead to reduce repetition and keep variable exports in one place.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Since many partials now `@use '../variables' as *;`, consider creating a central variables module that `@forward`s your tokens and `@use`s that instead to reduce repetition and keep variable exports in one place.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request migrates Sass @import statements to the @use rule across various component and layout files. The review feedback identifies that the migration is incomplete, as several partials referenced in style.scss were not updated, which could lead to 'Undefined variable' errors. Additionally, the switch to @use for Vuetify styles requires the use of the with configuration syntax to maintain existing variable overrides.

[gemini-code-assist]

The migration to @use appears to be incomplete. While several partials (like VButtons, VCard, and VShadow) were updated in this PR to include @use '../variables' as *;, others imported here—specifically VInput (line 10), VNavigationDrawer (line 11), VTextField (line 13), VScrollbar (line 15), CodeBlockDark (line 16), and dashboards (line 18)—were not included in the patch. If these files reference variables from _variables.scss, the build will fail with 'Undefined variable' errors because @use does not provide a global scope like @import did. Please ensure all partials are updated to explicitly load their dependencies.

[gemini-code-assist]

Switching from @import to @use for vuetify/styles/main.sass changes how variable overrides are handled. In Sass modules, variables defined in ./variables (such as $border-radius-root or $color-pack) are no longer automatically available to the Vuetify module. If these variables were intended to customize Vuetify's default styling, you must now use the with configuration syntax or ensure the variables are forwarded correctly. For example: @use 'vuetify/styles/main.sass' with ($border-radius-root: 8px);.