feat: change generic color class names

[nekosaur]

Description

// v2
.indigo
.indigo--text

.indigo.lighten-2
.indigo--text.text--darken-1

// v3
.bg-indigo
.text-indigo

.bg-indigo-lighten-2
.text-indigo-darken-1

Motivation and Context

This aligns generic color classes with those generated from the theme system, which means that the generic ones can be used in color prop without any additional work.

This is a breaking change.

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]

Other than my one question, looks good to me.

[johnleider]

do we still use accent?

[johnleider]

It looks good. What is our stance on the global .v-application class? I believe we talked about removing it.

[nekosaur]

I think it would make sense to make them global, since that's how the theme classes work

[johnleider]

I think it would make sense to make them global, since that's how the theme classes work

@KaelWD could you chime in?

[KaelWD]

Everything should be global in v3