fix(styles): deal with new sass restriction

[mcdmaster]

cf. https://sass-lang.com/documentation/breaking-changes/slash-div
To deal with this new SASS anti-slash-div facility

Fixes #13694
Fixes Tokyo-Metro-Gov/covid19#6346

Description

Motivation and Context

Other applications implementing SASS plus Vuetify are impacted on the change done by SASS

How Has This Been Tested?

Markup:

// Paste your FULL Playground.vue here

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Improvement/refactoring (non-breaking change that doesn't add any features but makes things better)

Checklist:

• The PR title is no longer than 64 characters.
• The PR is submitted to the correct branch (master for bug fixes and documentation updates, dev for new features and backwards compatible changes and next for non-backwards compatible changes).
• My code follows the code style of this project.
• I've added relevant changes to the documentation (applies to new features and breaking changes in core library)

[johnleider]

I checked the build on both this and master with my update and the files are identical. With that being said, we should probably opt to wrap our division in #{} as opposed to switching to multiplication. Either way, I'd still like @KaelWD to take a look at this.

[KaelWD]

Use math.div instead of muliplication

[KaelWD]

we should probably opt to wrap our division in #{}

This is deprecated too.

[KaelWD]

That means everywhere. If you want to propose testing changes that can be a separate pr

[Tofandel]

Wow, that's some big breaking change from sass.. I mean they could have opted for another character to handle grids... Instead of breaking every single division out there.. It would have seemed like the more reasonable approach

Oh well

[vercel]

@mcdmaster is attempting to deploy a commit to the Vuetify Team on Vercel.

A member of the Team first needs to authorize it.

[mcdmaster]

That means everywhere. If you want to propose testing changes that can be a separate pr

@KaelWD Done. Please check. Thanks

[johnleider]

This PR contains multiple commits that have nothing to do with this bug fix. Can you please remove them.

[johnleider]

Looking good. What is the reason behind the CI changes?

[mcdmaster]

@johnleider Thank you. BTW, I was not confident with my CI credentials properly registered.
Can you please let me know if it is better to withdraw the last commit of mine?

[KaelWD]

Build is failing and still shows some deprecation notices, please double-check your work.