Update uv-ebook-components to community standards

[jamesmisson]

In support of #1380, we need to do several things to bring @universalviewer/uv-ebook-components up to UV community standards:

• Update GitHub Actions to use up-to-date versions (including Node 20)
• Check for any other references to outdated Node versions (e.g. look in package.json and any tool-related configuration files)
• Update dependencies (pay special attention to typescript/webpack) and resolve outstanding Dependabot PRs where possible.
• Replace tslint with eslint; align configuration with UV project
• Update prettier and align configuration with UV project
• Review other PRs and merge if safe/ready
• Create a "main" branch and make it the default instead of "master"
• Retarget any remaining PRs against "main" instead of "master"
• Change any references to "master" in README, etc. to "main."
• Delete the "master" branch
• Release a new version of the component
• Upgrade the component upstream in UV

See recent PRs on https://github.com/IIIF-Commons/vocabulary for reference

[demiankatz]

As discussed on today's standup, I think we can repurpose this issue to remove the abandoned/unsupported ebook functionality. This is probably a matter of removing @universalviewer/uv-ebook-components from package.json, searching the code for references to this module and removing that code, and testing that after references have been removed, loading an ePub manifest goes to the generic file download module.

[LanieOkorodudu]

Keep manifest and improve the download

[demiankatz]

We will be abandoning uv-ebook-components in #1697, so there is no need to take further action.