Description of Pull Request:

Breaking the remaining bits of table into more manageable bits.

Also fixing up the sorting aria-label computation that was messed up with the introduction of sort-direction prop and field.sortDirection property (which need better documentation). It wasn't handing proper labeling of the non-sorted sortable columns (was labeling the wrong direction action 75% of the time). Adding in tests to ensure the expected labels do not get messed up (for accessibility reasons).

To Do:

• documentation update for the above mentioned prop and field property.
• filter testing
• sort testing (functionality and labels / attributes)
• pagination testing (functionality and labels/attributes)
• additional sanity tests to make sure attributes and classes are applied correctly
• provider testing (changing provider functions)
• migrate from legacy testing to vue-test-utils (table styles, responsive, stacked)

PR checklist:

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Enhancement to an existing feature
• ARIA accessibility
• Documentation update
• Other, please describe: code re-work

Does this PR introduce a breaking change? (check one)

• Yes
• No

If yes, please describe the impact:

The PR fulfills these requirements:

• It's submitted to the dev branch, not the master branch
• When resolving a specific issue, it's referenced in the PR's title (i.e.
  fixes #xxxx[,#xxxx], where "xxxx" is the issue number)
• The PR should address only one issue or feature. If adding multiple features or fixing a bug
  and adding a new feature, break them into separate PRs if at all possible.
• PR titles should following the
  Conventional Commits naming convention (i.e.
  "fix(alert): not alerting during SSR render", "docs(badge): Updated pill examples, fix typos",
  "chore: fix typo in docs", etc). This is very important, as the CHANGELOG is generated
  from these messages.

If new features/enhancement/fixes are added or changed:

• Includes documentation updates (including updating the component's package.json for slot and
  event changes)
• New/updated tests are included and passing (if required)
• Existing test suites are passing
• The changes have not impacted the functionality of other components or directives
• ARIA Accessibility has been taken into consideration (does it affect screen reader users or
  keyboard only users? clickable items should be in the tab index, etc)

If adding a new feature, or changing the functionality of an existing feature, the PR's
description above includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a
  suggestion issue first and wait for approval before working on it)