0.6.0 "Manifest V3, Types, and Tests"

0.6.0 is a "huge" release with Manifest V3 support and a rewrite to
TypeScript as its headline features.

This release has been manually tested on Chromium and Firefox.

Note that this version requires a minimum Chromium and Firefox version
of 121. This is the earliest version where both browsers will
(begrudgingly) ignore excess fields in the manifest.json file. This was
the blocker for Manifest V3 as this permits the neccessary fields to
keep the manifest.json as one file across browsers.

After a patch version to patch a bad version, I've decided to spend an
entire day migrating the code to something more sustainable --
Typescript and with decent testing capabilities. There's also more
logging in the console to further debug issues. Substaintial test
coverage is not part of this release, but I think we're in a good spot
to cut a release.

Importantly, TypeScript source files require significant revamp to how
the codebase is organized. Because there is now a transpilation stage,
the overall complexity of the codebase has increased, even if there is
no significant new features. While I mourn the loss of simplicity (you
could previously just point Firefox to the repo and it would work!),
having a proper testing framework is absolutely worth it.

Due to some workarounds needed for Chrome, I expect Chrome to
potentially have more bugs than Firefox. This is because we need to
create a hidden document, send a message to that document from the
service worker, and have that document recieve the message to then write
it to a DOM and use a deprecated way to copy text into the clipboard.
Yes, this is obtuse. Yes, this is also the way the Chrome blog
recommends doing this until they support what Firefox already does.

You'll notice that the permissions have changed as well! We no longer
require the tabs permission, just activeTab instead. This restricts the
extension so that it gets access to your tab data only when you press the
button. Hurray for privacy!

- Fixed "Constructor Set requires 'new'" error

- Fixed allowed protocols not working in extension options page

Shlinks created by the extension will now use the tab's name as the displayed title. No more long URLs!

This update is a breaking change and disallows using HTTP to talk to external Shlink instances.

Exposed the protocol filters. Now you can select to disable specific protocols from being Shlinked.

Added an option for shlinks created with this extension to be tagged for better link management.

New options are now available:
- You can now select to either always generate a new short url or use an existing one if it existed. Previously, you would always reuse an existing one.
- You can now choose to modify an existing short url and update the value to the current page you're on.

Removed an extra permission. This no longer asks for the all websites permission, as it was misunderstood and was unnecessary.