Update vcf-validator to 0.9.7 and add support for ARM on OSX

[tcezard]

Update of vcf-validator to v0.9.7
Add binaries for ARM architecture on OS-X

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

General instructions

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Instructions for avoiding API, ABI, and CLI breakage issues

Conda is able to record and lock (a.k.a. pin) dependency versions used at build time of other recipes.
This way, one can avoid that expectations of a downstream recipe with regards to API, ABI, or CLI are violated by later changes in the recipe.
If not already present in the meta.yaml, make sure to specify run_exports (see here for the rationale and comprehensive explanation).
Add a run_exports section like this:

build:
  run_exports:
    - ...

with ... being one of:

Case	run_exports statement
semantic versioning	{{ pin_subpackage("myrecipe", max_pin="x") }}
semantic versioning (0.x.x)	{{ pin_subpackage("myrecipe", max_pin="x.x") }}
known breakage in minor versions	{{ pin_subpackage("myrecipe", max_pin="x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
known breakage in patch versions	{{ pin_subpackage("myrecipe", max_pin="x.x.x") }} (in such a case, please add a note that shortly mentions your evidence for that)
calendar versioning	{{ pin_subpackage("myrecipe", max_pin=None) }}

while replacing "myrecipe" with either name if a name|lower variable is defined in your recipe or with the lowercase name of the package in quotes.

Bot commands for PR management

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

Note that the @BiocondaBot please merge command is now depreciated. Please just squash and merge instead.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.

[martin-g]

Support for OSX ARM64 is coming but not yet available!
See #46775

[tcezard]

Do you mean that the selector does not work ATM?

[martin-g]

The selector works but nothing will be build and uploaded for osx-arm64.

[tcezard]

Ok. Since we're distributing prebuilt binaries (see original discussion), I think we'll be ok then.

[martin-g]

I am not sure what you mean with we'll be ok.
As you can see the build produces conda packages for linux and osx x86_64 only.
The osx-arm64 stuff is ignored. But once it arrives you will just need to bump the build number.

[tcezard]

I see. Thank you for explaining.
Should I remove it from the build or leave it even if it does not get pulled ?

[martin-g]

As you prefer. It is just ignored at the moment, so it does not cause any harm.

[aliciaaevans]

The osx-arm64 builds have been enabled just now! You'll need to add the additional platform configuration: https://bioconda.github.io/developer/aarch64.html

[martin-g]

@BiocondaBot please fetch artifacts

[BiocondaBot]

Package(s) built are ready for inspection:

Arch	Package	Zip File / Repodata	CI	Instructions
linux-64	vcf-validator-0.9.7-h9ee0642_0.tar.bz2	LinuxArtifacts.zip	Azure	show You may also use conda to install after downloading and extracting the zip file. From the LinuxArtifacts directory: conda install -c ./packages <package name>
osx-64	vcf-validator-0.9.7-h527b516_0.tar.bz2	OSXArtifacts.zip	Azure	show You may also use conda to install after downloading and extracting the zip file. From the OSXArtifacts directory: conda install -c ./packages <package name>

---

Docker image(s) built:

Package	Tag	CI	Install with docker
vcf-validator	0.9.7--h9ee0642_0	Azure	show Images for Azure are in the LinuxArtifacts zip file above.gzip -dc LinuxArtifacts/images/vcf-validator:0.9.7--h9ee0642_0.tar.gz | docker load

[aliciaaevans]

@BiocondaBot please fetch artifacts

[BiocondaBot]

Package(s) built are ready for inspection:

Arch	Package	Zip File / Repodata	CI	Instructions
linux-64	vcf-validator-0.9.7-h9ee0642_0.tar.bz2	LinuxArtifacts.zip	Azure	show You may also use conda to install after downloading and extracting the zip file. From the LinuxArtifacts directory: conda install -c ./packages <package name>
osx-64	vcf-validator-0.9.7-h527b516_0.tar.bz2	OSXArtifacts.zip	Azure	show You may also use conda to install after downloading and extracting the zip file. From the OSXArtifacts directory: conda install -c ./packages <package name>

---

Docker image(s) built:

Package	Tag	CI	Install with docker
vcf-validator	0.9.7--h9ee0642_0	Azure	show Images for Azure are in the LinuxArtifacts zip file above.gzip -dc LinuxArtifacts/images/vcf-validator:0.9.7--h9ee0642_0.tar.gz | docker load

[aliciaaevans]

Had to merge in the changes from master to get the osx-arm64 build to run.