Describe the PR

Makes sorting by formatted value opt-in_ on a per-field basis, by adding a new field property sortByFormatted. Defaults to false. If true, then internal sorting will use the result of the field's formatter (if provided) for sorting.

This change is based on user feedback regarding the ability to sort virtual columns, and regular columns, and the preference to optionally enable this feature (i.e., opt-in).

PR checklist

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

• Bugfix
• Feature
• Enhancement
• ARIA accessibility
• Documentation update
• Other (please describe)

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

• No
• Yes (please describe) Behavioural change versus versions 2.0.0-rc.25 to 2.0.0-rc.27

Sorting by formatted value was introduced in v2.0.0-rc.25, but it was not opt-in. This PR makes sorting by formatted value opt-in, which is the opposite in version 2.0.0-rc.25 to .27.

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 #xxx[,#xxx]), where "xxx" is the issue number)
• It 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.
• The title should follow the Conventional Commits naming convention (i.e. fix(alert): not alerting during SSR render, docs(badge): update pill examples, fix typos, chore: fix typo in README, 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)
• Includes any needed TypeScript declaration file updates
• 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)