try to warn people about the evils of dynamically linking openssl

one option off the top of my head is to prompt to [setup cargo-deny](https://embarkstudios.github.io/cargo-deny/checks/cfg.html) on `cargo dist init`

Start at the cargo-dist init entry point and review how initialization prompts are defined. Read the linked cargo-deny checks documentation to determine how dynamically linked OpenSSL should be detected or communicated, then make cargo dist init provide the proposed warning or setup guidance and verify the resulting prompt behavior.

Written by the indexing model from the issue text.