BREAKING CHANGE: removal of deprecated es/ build directory

Describe the PR

This PR is for the 2.0.0 stable release, to remove the deprecated es/ build

To do:

• remove es/ build commands
• docs update
• remove legacy plugin exports and re-normalize components/index.js and directives/index.js files
• remove legacy es entrypoint index
• remove default exports from all component index.js files
• remove default exports from all directive index.js files
• move all component/directive/plugin re-exports to src/index.js
• Release stable build

PR checklist

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

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

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

• No
• Yes (please describe)

Users will no longer be able to import from the es/ build dirs. Users should be switching to the simplified import methods introduced in v2.0.0-rc.22. Legacy plugin names will no longer work as they were only exported from es/ build.

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)
• 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)