perf(table): minor tweaks to primary key usage

[tmorehouse]

Description of Pull Request:

Minor adjustments to row :key generation based on primary key existence.

Rather than use a serialized version of the row values as the rows :key value, the displayed row index value is used (unless a primary key is provided).

Users who are experiencing issues with components in cells getting re-used (and not fully updating, as in #931, and #2410) will need to specify a primary-key column to circumvent issues they may encounter. This PR partially reverts #2416 as using the primary-key will provide better results, as the serialized string (from the rows values) could change due to mutations in row data, causing unnecessary re-renders.

Also adds a row attribute data-pk which will have the primary key value.

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:

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

• Yes
• No
• Partially

If yes, please describe the impact:

Partial impact to users that may experience issues with components/elements being re-used when filtering/sorting/pagination. Providing a primary-key in the table data (or using keys on their components) will circumvent the issues.

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)

[codecov]

Codecov Report

Merging #2741 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #2741   +/-   ##
=======================================
  Coverage   74.89%   74.89%           
=======================================
  Files         176      176           
  Lines        3195     3195           
  Branches      942      942           
=======================================
  Hits         2393     2393           
  Misses        585      585           
  Partials      217      217

Impacted Files	Coverage Δ
src/components/table/table.js	74.16% <100%> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ab7937e...7c762ec. Read the comment docs.