Do not use git hashes for packages versioning

[tgorochowik]

• 92620c8 - Fixes Invalid packages versioning #59
• 7a90622 - Fixes Install conda-verify #45
• 3269832 - Fixes Fixes the sudos in the slang package #61
• A bunch of cleanup (conda-get script 7a90622, openocd cleanup 73ce178).

[tgorochowik]

Pushed a new version that concatenates the build date and the git hash to use it as the package version. This is more universal as the packages that don't use git tags failed with the previous approach and it is safer in terms of random tags that may appear in the repositories (see the original comment here).

I guess that if we want to add a more human readable version string to the package version we can do that individually for each package (but still make sure it is not the very first part of the version string so it gets sorted properly).

[mithro]

{% set version = '%s_%04i_%s'|format(GIT_DESCRIBE_TAG|replace('v', '') or '0.X', GIT_DESCRIBE_NUMBER|int, GIT_DESCRIBE_HASH or 'gUNKNOWN') %}

[mithro]

See the other meta.yml files for how version should be handled.

[mithro]

@tgorochowik - I've reworked you changes and gotten most of the upstream projects to add tags (tree-sitter/tree-sitter-verilog#38, MikePopoloski/slang#273, zachjs/sv2v#58). I've also gotten Icarus buffer overrun fixed (steveicarus/iverilog#287).