feat(VDivider): port to v3

[johnleider]

Description

More to follow..

fixes #12054

Motivation and Context

Port v-divider to v3

How Has This Been Tested?

jest

Markup:

https://gist.github.com/johnleider/9b501dc94fa13e75ed339f425613f115

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]

Requesting Initial comments from @vuetifyjs/contributors @vuetifyjs/core-team

[johnleider]

Requesting Final comments from @vuetifyjs/contributors @vuetifyjs/core-team

[nekosaur]

I'm not entirely on board with the current API of v-divider. Assuming everything works correctly, the following markup

<v-divider width="100px" height="100px" border></v-didiver>

Would result in a 100x100px box with border on all sides. That seems very far from what v-divider should be and do.

Additionally, markup like this

<v-divider width="100px"></v-divider>

Would result in something like this in horizontal mode

And this in vertical mode

since width/height are orientation dependent.

In my mind, the props

border
width
height
maxWidth
maxHeight

could be replaced by

thickness
length
color (if we want to keep that functionality from border)

and better represent the function of the component