Infer minimum Gleam version

[giacomocavalieri]

This PR closes #3492

It's still a WIP because I have some questions before I can move forward:

1. I used the Version type that comes from hexpm::version, should we use our own minimal custom type instead of relying on this one?
2. If someone specifies an insufficient version (let's say gleam.toml has 1.2 but we inferred the minimum one to be 1.5) how should the error be presented to the user?
   Do we want the error message to include an example of a usage of a feature that explains why we inferred that number? For example something that looks like this:

   error: invalid Gleam version
   
   1 | tuple.0.1
            ^^^^
   
   Nested tuple access requires a Gleam version >= 1.2 but the version specified in
   your `gleam.toml` is 1.1!

   Even if someone used multiple features I think it would be better to show just one, I don't think there's much value in making the error message any longer
3. What if the gleam.toml doesn't specify any gleam version? Do we want to manually add the constraint when publishing it or have an error and force the programmer to explicitly write the inferred version down? Is there any downside to doing it implicitly?

[lpil]

Heya! I've not looked at the code yet but here's my thoughts on the Qs:

1. Hex one is fine.
2. Warn for analysis, error for publishing. We show all warnings rather than stopping after the first instance as the programmer wants to know about all of them so they can fix it. Seems like it might be tricky working out what the requirement means as it can be of arbitrary complexity such as >= 1.0.0 and < 3.0.0 or >= 4.0.0 and < 5.0.0.
3. Add our own when publishing seems fine to me.

[lpil]

Beautiful work as per usual!!!! 💜