docs: Mention required openssl dep for rust-script

[mbargull]

Description

https://github.com/snakemake/snakemake/blob/v6.9.1/snakemake/script.py#L1142 needs the json_typegen Crate which pulls in ( https://github.com/evestera/json_typegen/blob/v0.7.0/json_typegen/Cargo.toml#L19 ) its own library/Crate json_typegen_shared and that one by its default features pulls in reqwest ( https://github.com/evestera/json_typegen/blob/v0.7.0/json_typegen_shared/Cargo.toml#L24 ) which further down the road depends on OpenSSL (see cargo tree for json_typegen for the dependency tree).
So, OpenSSL is not a rust-script dependency here, but one that Snakemake-generated Rust "scripts" need.

We should also ask (i.e., issue or if possible PR) the json_typegen maintainers to propagate json_typegen_shared feature selection to json_typegen, i.e., ask to add a feature to json_typegen to deactivate json_typegen_shared's remote-samples feature (possibly also the other default features local-samples, option-parsing then; but those don't concern the OpenSSL problem here).

QC

• The PR contains a test case for the changes or the changes are already covered by an existing test case.
• The documentation (docs/) is updated to reflect the changes or this is not necessary (e.g. if the change does neither modify the language nor the behavior or functionalities of Snakemake).

[mbargull]

Fails with

error: /home/runner/.cache/rust-script/binaries/release/deps/libjson_typegen-e57fc97d05e82a5a.so: undefined symbol: FIPS_mode_set

which smells like custom Red Hat OpenSSL ... No idea where it picked that one up O_o

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[mbargull]

If evestera/json_typegen#34 lands in a json_typegen release, we should be set with only rust-script, depend on the json_typegen crate with default-features = false and could then remove these doc/test changes again.

Though we could then think about what to do to make this more convenient for the -- probably not that uncommon -- cases that use/depend/build C libraries on-the-fly (e.g., @FelixMoelder already encountered this with a rust-script that used rust-htslib at snakemake-workflows/dna-seq-varlociraptor#80 ). For the Conda environment-based workflows we could make a (meta) package snakemake-rust-script-or-similarly-named that just carries these dependencies and then put in the docs not rust-script but snakemake-rust-script as the dependency that users should put into their env.yml files.