First version release

[anonrig]

Let's wait until the Node.js pull request is merged to release the v1.0.0

Fixes #207
Fixes #142

[lemire]

@anonrig Tests fail with a ccache error?

[anonrig]

It seems Azure is having some issues:

Err:1 http://azure.archive.ubuntu.com/ubuntu focal/main amd64 ccache amd64 3.7.7-1
[27](https://github.com/ada-url/ada/actions/runs/4104094755/jobs/7079124017#step:3:28)
    Connection failed [IP: 52.147.219.192 80]

[lemire]

It looks like it is still failing...

The following NEW packages will be installed:
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:9)
  ninja-build
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:10)
0 upgraded, 1 newly installed, 0 to remove and 14 not upgraded.
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:11)
Need to get 107 kB of archives.
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:12)
After this operation, 338 kB of additional disk space will be used.
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:13)
Err:1 http://azure.archive.ubuntu.com/ubuntu focal/universe amd64 ninja-build amd64 1.10.0-1build1
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:14)
  Connection failed [IP: 40.119.46.219 80]
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:15)
E: Failed to fetch http://azure.archive.ubuntu.com/ubuntu/pool/universe/n/ninja-build/ninja-build_1.10.0-1build1_amd64.deb  Connection failed [IP: 40.119.46.219 80]
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:16)
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
(https://github.com/ada-url/ada/actions/runs/4104251833/jobs/7079480086#step:5:17)
Error: Process completed with exit code 100.

It needs to install Ninja and can't.

[anonrig]

Re-running the workflows one by one fixed the issue. It seems it was a temporary issue with Azure networks.