Migrate built-in functions that are deprecated from Sass

What does this MR do and why?

Global built-in functions were deprecated and will be removed in Dart Sass 3.0.0.

This was automated by sass-migrator module --built-in-only.

Automated migration

This migration was fully automated. I used the following commands:

sass-migrator module --built-in-only app/assets/stylesheets/**/*.scss --load-path $(pwd)/node_modules --load-path $(pwd)/node_modules/@gitlab/ui/src/vendor --load-path $(pwd)/app/assets/stylesheets
sass-migrator module --built-in-only app/assets/stylesheets/**/**/*.scss --load-path $(pwd)/node_modules --load-path $(pwd)/node_modules/@gitlab/ui/src/vendor --load-path $(pwd)/app/assets/stylesheets
sass-migrator module --built-in-only ee/app/assets/stylesheets/**/*.scss --load-path $(pwd)/node_modules --load-path $(pwd)/node_modules/@gitlab/ui/src/vendor --load-path $(pwd)/app/assets/stylesheets
sass-migrator module --built-in-only app/assets/stylesheets/bootstrap_migration_components.scss
git add .
yarn lint:stylelint:staged:fix

Why now?

While working with vite, we see many deprecation warnings that make vite logs hard to follow. Part of #557045 (closed)

Warnings look like this:

References

• https://sass-lang.com/documentation/breaking-changes/import/
• https://sass-lang.com/documentation/cli/migrator/#global-options

Screenshots or screen recordings

NA

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #557045 (closed)