This pull request adds a `mix error_tracker.install` task that installs
the error tracker using [Igniter]. This task automates the installation
and configuration steps detailed in the [Getting Started] guide by:
1. Adding ErrorTracker as a dependency
2. Updating `config.exs` to configure the ErrorTracker application
3. Create a new DB migration to set up the ErrorTracker tables
4. Update the `router.ex` file to mount the ErrorTracker dashboard

<details>
<summary>Here is the output <code>mix igniter.install
error_tracker</code> in a project named <code>wadus</code></summary>

```
Updating project's igniter dependency ✔
checking for igniter in project ✔
compiling igniter ✔
setting up igniter ✔

Update: mix.exs

     ...|
34 34   |  defp deps do
35 35   |    [
   36 + |      {:error_tracker, [path: "/Users/crbelaus/Developer/error-tracker", override: true]},
36 37   |      {:igniter, "~> 0.5", only: [:dev, :test]},
37 38   |      {:phoenix, "~> 1.7.21"},
     ...|


These dependencies should be installed before continuing. Modify mix.exs and install? [Y/n] Y
compiling error_tracker ✔
`error_tracker.install` ✔

The following installer was found and executed: `error_tracker.install`:

Update: config/config.exs

     ...|
 8  8   |import Config
 9  9   |
   10 + |config :error_tracker, repo: Wadus.Repo, otp_app: :wadus, enabled: true
   11 + |
10 12   |config :wadus,
11 13   |  ecto_repos: [Wadus.Repo],
     ...|


Update: lib/wadus_web/router.ex

     ...|
19 19   |
20 20   |    get "/", PageController, :home
   21 + |    # TODO: This path should be protected from unauthorized user access
   22 + |    error_tracker_dashboard("/errors")
21 23   |  end
22 24   |
     ...|


Create: priv/repo/migrations/20250405160735_add_error_tracker.exs

1 |defmodule Wadus.Repo.Migrations.AddErrorTracker do
2 |  use Ecto.Migration
3 |
4 |  def up, do: ErrorTracker.Migration.up()
5 |  def down, do: ErrorTracker.Migration.down(version: 1)
6 |end
7 |


Proceed with changes? [Y/n] Y

Successfully installed:

* error_tracker
```
</details>

This task can be used in two ways:
1. If you already have an existing Phoenix project run `mix
igniter.install error_tracker`\
   Take a look at the [mix igniter.install] docs
3. If you are creating a new Phoenix project run `mix igniter.new
app_name --install error_tracker --with phx.new`\
   Take a look at the [mix igniter.new] docs

[Igniter]: https://hexdocs.pm/igniter/Igniter.html
[Getting Started]:
https://github.com/elixir-error-tracker/error-tracker/blob/main/guides/Getting%20Started.md
[mix igniter.install]:
https://hexdocs.pm/igniter_new/Mix.Tasks.Igniter.Install.html
[mix igniter.new]:
https://hexdocs.pm/igniter_new/Mix.Tasks.Igniter.New.html

We thought about it and came to the conclusion that it would be good to
change the type declaration for the module. Open for discussion, because
that could potentially be a breaking change of the library if users
previously had implementations of `ErrorTracker.Ignorer` that matched on
non-string types (although, arguably those implementations would never
have worked).

This addresses #153.

---------

Co-authored-by: Manmohan Krishna <manmohan.krishna@maersk.com>

The ErrorTracker assets were compiled against an old (pre 1.0) version
of LiveView. This caused issues in applications using LiveView 1.0 and
newer.

This commit gets rid of the warning about LiveView and ErrorTracker
javascript version mismatch. We now follow LiveDashboard and Oban Web
footsteps and import the LiveView assets directly.

Ecto SQL 3.13 includes a fix that adds support for JSON backed arrays on
MariaSQL. This fixes some errors that MariaSQL users where encountering
when using breadcrumbs.

Fixes #150