Ignoring archived package versions when querying the registry

[Michael-F-Bryan]

Description

This PR updates the WapmSource to respect a package version's isArchived field. All packages with isArchived set will now be ignored while determining which versions satisfy the query.

Context

We were seeing #4000 because of a combination of semver quirks and not respecting a package version's isArchived flag:

• When running a package without a version constraint (i.e. wasmer run wasmer/python instead of wasmer run wasmer/python@3.12.0) we use the catch-all * version constraint to say "just give me the latest version".
• You need to explicitly ask for pre-release versions - they won't be picked up by *
• As far as semver is concerned, pre-releases (e.g. 3.12.0-build.5 or 3.12.0-beta) are considered to have a lower version number than their released version (i.e. 3.12.0).
• The WapmSource wasn't respecting the isArchived flag when looking for packages that satisfy a constraint

This all meant that when faced with the following versions for wasmer/python...

• 3.12.0-build.5
• 3.12.0-build.2 (archived)
• 3.12.0 (archived)
• 3.12.0-build.4 (archived)
• 3.12.0-build.3 (archived)

... We'll always pick version 3.12.0 (which is broken) because it has the "highest" version number that matches *.

Hence why running wasmer run wasmer/python would fail but explicitly wasmer run wasmer/python@3.12.0-build.5 would work.

Fixes #4000