Hide retired packages

[ffigiel]

Closes #18

This PR adds two things:

• Retired versions will not be selected when syncing packages
• The syncing process will try to delete packages when no valid versions are present

[ffigiel]

Running codegen changed the generated sql.gleam file a lot, I'm not sure if it's intended

[ffigiel]

I'm not sure if this behavior is what we want, and I should improve error handling

[lpil]

Can we hide them rather than deleting them please? 🙏

Weird how the ordering of the functions in the generated module has changed. Maybe we should make it sort them by name to avoid this in future.

[ffigiel]

@lpil I just found that there is a table named hidden_packages, should I add an entry there when all releases of a package are retired? What if a new release is made and it's not retired, should I remove the package from the hidden_packages then?

Before this discovery, I was planning to add an is_retired column to the packages table and use that, but maybe it's not necessary?

[lpil]

That table is for packages that have been deliberately hidden by us rather than retired by the package maintainer. I think it would be tricky to make that table mutable and not accidentally remove its contents thinking they are not retired.

Let's use the retirement field on releases. I don't think we'll have performance problems querying both tables, so we can avoid making a cache on the packages table for now.

[ffigiel]

Oh, I did not realize we had the retirement state in the database. This will make things easier 🙂
I have an initial version up, but it seems my query does not behave as expected (e.g. gleam_erlang is not shown anymore). I'll fix that and add some more tests
edit: Ready!

[lpil]

Could you instead make a non_retired_packages view? I think that would be easier to use and it wouldn't have to read the entire table to filter a single package. Thank you

[ffigiel]

It is done! (I learned some new things about sqlite along the way but it seems to work).

I had to adjust the text search query because sqlite views don't have rowids, but the search seems to behave the same way as it does in production.

[lpil]

Thank you. One small thing below

[lpil]

A package is retired if all its releases are retired. Something like this:

create view non_retired_packages as
select
  p.id
, p.name
, p.description
, p.docs_url
, p.links
, p.updated_in_hex_at
from packages p
where p.id in (
  select distinct r.package_id
  from releases r
  where r.id is null or r.retirement_reason is null
);

[ffigiel]

oops! Fixed, thanks for the explanation

[lpil]

Thank you!