Do not perform conda-forge output validation

[jdblischak]

Closes #223

Not needed for this feedstock that isn't a part of conda-forge, and also started failing recently for unknown reasons

https://conda-forge.org/docs/maintainer/infrastructure/#output-validation-and-feedstock-tokens https://conda-forge.org/docs/maintainer/conda_forge_yml/#conda-forge-output-validation

The latest tiledb binaries (https://anaconda.org/conda-forge/tiledb/files) built from the latest migration (https://github.com/conda-forge/tiledb-feedstock/pull/368) were uploaded only minutes ago. If we get conda solver errors, just need to restart the build.

Also heads up that we don't need to worry about the tiledb pins being added back to the .ci_support/ YAML files. I haven't been able to figure out what is causing this change in behavior, but those pins are overriden by our direct pins in meta.yaml, so they can be safely ignored.

[jdblischak]

The CDN cloning is degraded (status), so we're pretty much guaranteed to get the solver errors

[jdblischak]

I restarted the jobs to fix the conda solver error. CI is green