feat(BTable): Enable more sorting options to get closer to BSV parity

[dwgray]

Describe the PR

There were a few issues with table sorting compared to BSV:

• The sortDesc flag wasn't respected
• The sortByFormatted field wasn't used
  • And the sortByFormatted field didn't allow passing in a formatter function

I also added tests to cover these cases and updated the type documentation.

Small replication

Any sorted table example will replicate these issues. See the tests in this PR for concrete examples.

PR checklist

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

• Bugfix 🐛 - fix(...)
• Feature - feat(...)
• ARIA accessibility - fix(...)
• Documentation update - docs(...)
• Other (please describe)

The PR fulfills these requirements:

• Pull request title and all commits follow the Conventional Commits convention or has an override in this pull request body This is very important, as the CHANGELOG is generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[VividLemon]

I assume this functionality still is working in return ( realVal(a).localeCompare(realVal(b), props.sortCompareLocale, props.sortCompareOptions) * (sortDescBoolean.value ? -1 : 1)

[dwgray]

Yes - we had a case "conflicting" PRs that solved the same problem in ways that didn't actually cause a conflict in the diffs. My unit tests caught this. I left the way that I solved it in, as I think it's slightly cleaner (but I'm not a native JS developer, so if you'd prefer doing the explicit reverse at the end rather than sorting in the correct direction in the first place, I'll swap it out.